The information in this article applies to:
SYMPTOMS
Advanced: Requires expert coding, interoperability, and multiuser skills.
CAUSEThis problem occurs only if you have installed the Microsoft Access version 2.0 Service Pack. This problem is caused by the Microsoft SQL Server ODBC driver, but occurs only if you are using the Microsoft Jet database engine version 2.5, which is installed with the Service Pack. The problem with the SQL Server driver causes the Microsoft Jet database engine version 2.5 to be unable to link (attach) any table with a name with the following pattern:
Therefore, you can link a table with the name
but you cannot link a table with the name:
RESOLUTIONTo work around this problem, rename the table so that it does not have a name matching the pattern described in the "Cause" section. Or, create a SQL Server view based on the table and then link the view. For example, you could use the following sample SQL statement to create a view:
You could then link the view instead of linking the table. In order to
update the view, you would need to create an index specification on the
view, as in the following example:
For more information about this type of index, please see the Microsoft
Access "User's Guide," version 2.0, Chapter 9, "Importing, Exporting, and
Attaching," page 169.
STATUSThis problem no longer occurs with the ODBC SQL Server driver that ships with Microsoft Access 7.0 or 97 and SQL Server 6.x. REFERENCESFor more information about the Microsoft Access version 2.0 Service Pack, please see the following article in the Microsoft Knowledge Base: Q122927 WX1124: Microsoft Access Version 2.0 Service PackFor more information about the latest ODBC drivers available, please see the following article in the Microsoft Knowledge Base: Q147192 Which ODBC Driver Do I Use and Where Do I Get It? Additional query words: jet25 jet 2.5
Keywords : kberrmsg kbusage OdbcSqlms |
Last Reviewed: July 13, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |