BUG: CREATE TABLE and CREATE INDEX Cause Error 42000

Last reviewed: September 9, 1996
Article ID: Q124363
The information in this article applies to:
  • Microsoft Open Database Connectivity, version 2.0

BUG# QJET: 1824 (2.00.2317)

SYMPTOMS

Using the Microsoft Access ODBC driver, when the CREATE TABLE or CREATE INDEX commands are executed with table, column, or index names that contain words (such as, proc or view) anywhere in their name, an error is generated with SQLSTATE=42000:

   Syntax error or access violation.

STATUS

Microsoft has confirmed this to be a problem in ODBC Access Driver version 2.00.2317. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

This problem does not occur on the 3.40.2204 version of the driver. However, you still can not create an object whose name is exactly 'proc' or

'view' (note: view is, after all, an ODBC reserved word).

MORE INFORMATION

For example, the following statements cause the error:

   create table review(test <datatype>)
   create table viewing(test <datatype>)
   create table 'reviewing'(test <datatype>)
   create table <tablename> ('reviewing' <datatype>)
   create index review on <tablename>(<columnname>)

Calling SQLError returns:

   SQLSTATE=42000,
   szErrorMsg=[Microsoft][ODBC Microsoft Access 2.0 driver]Syntax error
   or access violation.

You will also get the above error for other identifiers containing the word "proc" anywhere in their name, such as myproc, processing, process, and so forth.

NOTE: If such a table or index already exists in the Microsoft Access .MDB file, then SELECT, DELETE, INSERT, and UPDATE queries will work fine with these identifiers.


Additional reference words: 2.00.2317 3.40 mfc visual C++ MSVC Windows NT
KBCategory: kbprg
KBSubcategory: odbc



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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.