Your Role in Working with a Record View
| Overview | How Do I | FAQ | Sample | | ODBC Driver List
The table below shows what you typically must do to work with a record view and what the framework does for you.
Working with a Record View: You and the Framework
| You... | The framework... |
| Use the Visual C++ dialog editor to design the form. | Creates a dialog template resource with controls. |
| Use ClassWizard to create classes derived from and or from and . | Writes the classes for you. |
| Use ClassWizard to map record view controls to recordset field data members. | Provides DDX between the controls and the recordset fields. |
| Provides default command handlers for Move First, Move Last, Move Next, and Move Previous commands from menus or toolbar buttons. | |
| Updates changes to the data source. | |
| [Optional] Write code to fill list boxes or combo boxes or other controls with data from a second recordset. | |
| [Optional] Write code for any special validations. | |
| [Optional] Write code to add or delete records. |
Form-based programming is only one approach to working with a database. For information on applications using some other user interface, or no user interface, see the articles MFC: Using Database Classes with Documents and Views and MFC: Using Database Classes Without Documents and Views. For alternative approaches to displaying database records, see classes and as well as the MFC Database sample .