Microsoft KB Archive/218995

= BUG: Error "Invalid Object Name" on Linked Server Table Through OLEDB =

Article ID: 218995

Article Last Modified on 10/29/2003

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition
 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q218995



BUG #: 47364 (SQLBUG_70) BUG #: 32019, 31233 (MDAC Bugs) BUG #: 47364 (SHILOH)



SYMPTOMS
The following error occurs when you attempt to modify (insert, delete, update) data in a SQL linked server table object:

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid Object Name. 'TestLinkedServer...TestTable'

These errors occur when you attempt to modify the data in a SQL Server 7.0 linked server table object through the SQL OLE DB Provider. Examples of using the SQL OLE DB Provider to view and change data are:
 * In browse mode in the SQL Server Enterprise Manager or through any other OLE DB driven user interface.
 * When connecting through the SQLOLEDB provider to SQL Server, through code. For example, use ActiveX Data Objects (ADO) to connect to a SQL Server using the SQL OLEDB provider, SQLOLEDB.



CAUSE
The SQL OLEDB Provider IColumnRowset:GetColumnsRowset interface does not currently recognize the new four part naming convention, introduced in SQL 7.0. This four part naming convention is used to select and update data in linked servers.



WORKAROUND
To modify data in a linked server table, use Transact-SQL to perform insert, update and/or delete actions against these objects.

When accessing SQL Server through code using the SQL OLEDB Provider, use a stored procedure located on the SQL Server to execute against a linked server.



STATUS
Microsoft has confirmed this to be a problem in SQL Server versions 7.0 and 2000, and Microsoft Data Access Components versions 2.0 and 2.1.

Keywords: kbbug kbpending KB218995

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.