ODBC Driver Guide

Previous Topic

Next Topic

Migration to c-treeACE SQL ODBC

With more and more traditional c-tree users leveraging the power of c-treeACE SQL, FairCom has labored to keep this transition as easy as possible. While we strive for the utmost in compatibility, we occasionally find areas where it is possible to encounter unexpected situations. The c-tree ODBC and c-treeACE SQL ODBC drivers are both fully standards compliant, however, subtle differences do exist. We have summarized these differences here.

  • All table names returned by the c-treeACE SQL ODBC Driver are as ‘owner.tablename’ without regard to the server configuration option SQL_OPTION OWNER_FILE_NAMES
  • The SQL_OPTION OWNER_FILE_NAMES only affects the name of the table created on disk. It determines whether the owner name is pre-pended to the physical table name or not. Table names returned by the ODBC driver are not affected by this c-treeACE SQL option.
  • Using the c-tree ODBC driver it was common practice to represent the symbolic table name in uppercase. You can use uppercase table names in c-treeACE SQL as long as you do not wrap them in double quotes.

    Another option is to use the SQL_OPTION DB_CASE_INSENSITIVE keyword before creating the template database and the c-treeACE SQL databases.