Installing Database Support

When you run Setup for Visual C++ .NET, the following database components are installed automatically:
All the necessary ATL OLE DB components. For more information, see Installing ATL Database Support.
A set of ODBC drivers with the ODBC driver manager and the ODBC administrator program. For more information, see "ODBC Drivers Installed" and "ODBC SDK Components Installed" in Installing MFC Database Support.
Necessary components from the DAO software development kit (SDK). This includes Help files, which are not integrated with this documentation. However, if you work with DAO, you need to install a version of Jet compatible with your operating system. For more information, see "DAO SDK Components Installed" in Installing MFC Database Support.
As part of the baseline installation, Setup also installs Microsoft Data Access Components (MDAC), which are necessary to support data access programming in Visual C++ .NET.
Visual C++ .NET installs the MDAC 2.7 SDK. You should check the Microsoft Universal Data Access Web site at http://microsoft.com/data/ for updates to and news about the MDAC SDK.
If you are redistributing data access applications, you should also have the MDAC 2.7 redistribution program. The MDAC 2.7 SDK is designed for use with the MDAC 2.7 redistribution program (Mdac_typ.exe) included in the MDAC directory on the Visual Studio .NET Prerequisites CD-ROM. You can also download Mdac_typ.exe from the MDAC 2.7 SDK download link previously listed. For more information about redistributing components, see Redistributing Controls.
Record (Data Access)
A record is a collection of data about a single entity, such as an account or a customer, stored in a table (a row of the table). A record consists of a group of contiguous columns (sometimes called fields) that contain data of various types. A set of records selected from a data source — often called a result set in database terms — is called a recordset in MFC. For more information, see Recordset (ODBC).Schema (Data Access)
A database schema describes the current structure of the tables and database views in the database. In general, wizard-generated code assumes that the schema for the table or tables accessed by a recordset will not change, but the database classes can deal with some schema changes, such as adding, reordering, or deleting unbound columns. If a table changes, you must manually update the recordset for the table, then recompile your application.
You can also supplement the wizard-generated code to deal with a database whose schema is not entirely known at compile time. For more information