|
|
|
ODBC compliant applications, such as Microsoft Query, keep their own internal list of supported drivers. Therefore, if you remove a driver from the Windows ODBC setup icon, the driver will still appear in the Microsoft Query internal driver list. See your ODBC compliant application instructions for the specific procedures used to remove ODBC drivers from its internal list.
Most ODBC compliant applications provide a mechanism for searching to the first or last record of a file. If a multi-file search does not have file relationships defined, or if they are defined incorrectly, the search may take a long time. For example, if a report listing one field from each of the four files in the c-tree ODBC tutorial was executed without file relationships, it could take several minutes. The ODBC application will search all permutations of field cross-referencing in an effort to establish a proper link. To prevent extended search times, ALWAYS define file relationships for multi-file operations.
When creating multiple database references in the ODBC Dictionary, CTSYSCAT.FCS, it may be necessary to exit the ODBC compliant application in between creating dictionaries. For example, to create a dictionary entry named CUSTOMER, create a script named CUSTOMER.DB and place it in the directory specified by the Data Dictionary Path setting. Start an ODBC compliant application, such as Microsoft Query. When the ODBC Driver referencing CUSTOMER.DB as the Script Name is selected, the dictionary will have CUSTOMER entered as a valid database name. Before creating a new dictionary entry by referencing a new script, first exit the ODBC application (i.e., Microsoft Query in this example).
The c-tree 32-bit ODBC Driver configuration automatically creates a file DSN during installation, and updates it when saving the current ODBC driver configuration.
