﻿Application requires that we build tabs, panels, controls from database.  In other words, another application builds the user interface and writes all the tabs, panels, and controls to a database.  This application reads the database to determine what the user interface looks like and then builds the user interface dynamically.


The real screen has several modes: query, view, new, and edit.

Query mode: user can enter search criteria and then click the search push button

View mode: After searching, data is returned and viewed.  User can see detailed data at top and list of data in data grid at bottom

New mode: user can enter data for a new record that is then saved into the database

Edit mode: user can edit existing record in the database


NOTE: txtTextBoxValues is a temporary textbox used for testing only.  It proves that after a postback, we can regenerate the screen and read the values that the user entered on the screen
 


At the top of the screen are data navigation controls that allow the user to move through the detailed data one record at a time, jump to beginning, jump to end, etc

The upper part of the user interface (in the web tabs) is a "details view" of the current record.

The "details view" can display one record of data OR be cleared and then user can enter search criteria for a new search OR user can enter data for a new record OR edit an existing record

The lower part of the user interface (in the data grid) is a "grid view" of all the current records.  The current record should be selected in the data grid.

The grid needs paging support.  


Some of the web tabs will enable a button in the data grid that allows the user to popup a document viewer to view a document tied to that row of the data grid

