Potential Pitfalls of ODBC Databases

All ODBC databases are not created alike! MGI can only use the tools that are available in the ODBC database driver. The following are some pitfalls that you may encounter when implementing MGI with an ODBC database.

  1. Some ODBC databases will not allow the creation of new databases through ODBC drivers. With these databases you will have to do all database creation using the ODBC database's proprietary interface or application.
  2. Some ODBC databases will not allow field management through ODBC drivers. With these databases you will have to do all database field layout using the ODBC database's proprietary interface or application.
  3. MGI can only use the fields types that are available via the ODBC's driver. Even if the database supports many different field types in its proprietary interface, the database's driver may not necessarily support all of those field types via ODBC. This lack of field types could cause problems for some tags that require predictable field types to store their internal data.
  4. Some databases do not provide an efficient way to count records. Some databases also do not provide an efficient way to position on a certain record. The mgiEditDatabase tag and any other tags that produces a record/result count or that iterates through records may perform poorly with such databases.


[Return to the Using ODBC Databases Menu]


[Understanding MGI Menu] [Using MGI Menu] [Referencing MGI Menu]


[MGI Guides Main Menu] [User Guide Main Menu]