ACC95: Btrieve ODBC Error "Table is Not Defined in Dictionary"

Last reviewed: May 30, 1997
Article ID: Q156221
The information in this article applies to:
  • Microsoft Access version 7.0
  • Microsoft Access Developer's Toolkit versions 2.0, 7.0

SYMPTOMS

Advanced: Requires expert coding, interoperability, and multiuser skills.

The BTI ODBC Driver version 1.0.1 may return error 204:

   Table is Not Defined in Dictionary

This error generally occurs with a catalog function, such as SQLGetInfo(). This can occur in both the 16- and 32-bit versions of the BTI ODBC driver.

CAUSE

A catalog function, such as SQLGetInfo(), causes the ODBC interface to return a backslash (\) as the SQL_SEARCH_PATTERN_ESCAPE character. This means the backslash may indicate that certain characters that follow are interpreted as literals in search patterns.

When Microsoft Access generates an SQL statement that contains the backslash followed by the literal characters, the search is performed on the full string, including the backslash. This causes the search to fail and produces the error.

RESOLUTION

A patch is available from Pervasive Software, formerly known as Btrieve Technologies, in their Compuserve forum [GO Btrieve]. The update version is v1.0.3, and is in a self-extracting file called Odbcv103.exe.

MORE INFORMATION

The BTI ODBC driver is manufactured by Pervasive Software, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.


Additional query words: SQL ADT attach link

Keywords : kb3rdparty OdbcNonms
Version : 7.0
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.