Saving the DBCtrlGrid for last makes the most sense, as the component itself is a container for a select group of the other data-aware controls. DBCtrlGrid begins with the fundamental concept of the grid, that is, to display a number of columns of numerous rows simultaneously. This data is configured in a very familiar table layout that conveys the information to the user simply and clearly once they have divined the relationship between the rows and columns. The control grid begins with this premise and then kicks it up several notches.
The DBCtrlGrid control is composed of panels on which a selection of the other data-aware (or non-data-aware) controls can be placed. At design time, the controls on the panel represent a single row in the dataset. At run time, however, the layout that you create is duplicated for every row in the underlying dataset, filling the component with a view of multiple fields from multiple records. The navigation controls that are used will cause the display to skip from panel to panel.
The DBCtrlGrid component provides a unique interface opportunity for your applications. If single field controls are placed directly upon a form, the user can only view a single record in that format at a time. There are many times when this is appropriate. In some cases, however, the information is better presented as discrete fields but in a way that more than one row of the database can be displayed at one time. For these times, Borland has included the DBCtrlGrid.
Was this article helpful?