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

ID: Q218995


The information in this article applies to:
  • Microsoft SQL Server version 7.0

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

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 version 7.0 and Microsoft Data Access Components version 2.0 and 2.1.

Additional query words:

Keywords : kbbug7.00 kbSQLServ700bug
Version : winnt:7.0
Platform : winnt
Issue type : kbbug


Last Reviewed: September 21, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.