ACC2000: "ODBC--Connection to 'DataSourceName' failed" Error Message Occurs When Opening Linked Oracle Tables (325835)


The information in this article applies to:

  • Microsoft Access 2000
This article was previously published under Q325835
Moderate: Requires basic macro, coding, and interoperability skills.

This article applies only to a Microsoft Access database (.mdb).

SYMPTOMS

The following error message may occur when you open a linked Oracle table in a Microsoft Access database:
ODBC--Connection to 'DataSourceName' failed.
The earlier error message is followed by another error message:
Microsoft Access cannot open the table in Datasheet view.

CAUSE

The error messages may occur when all of the scenarios below are true:

  • The Oracle tables are linked by using the Microsoft Open Database Connectivity (ODBC) Driver for Oracle.
  • The linked tables are refreshed by using the Linked Table Manager.
  • You open the linked Oracle table.
When you relink Oracle tables, the Linked Table Manager adds the following syntax to the connection string of the linked Oracle tables: 
"Database="
If the Always Prompt for New Location check box in the Linked Table Manager is selected, the problem does not occur with the first linked Oracle table. The problem does occur with the remaining linked tables. If this check box is not selected, the problem occurs with all of the linked Oracle tables.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce the Behavior

  1. Create a data source name (DSN) by using the Microsoft ODBC Driver for Oracle.
  2. Create a Microsoft Access 2000 database, and then link two Oracle tables to the database by using this DSN.
  3. Use the Linked Table Manager, to refresh the table links with the Always Prompt for New Location selected.
  4. Exit and then restart Microsoft Access.
  5. Open the database, and then try to open the second linked table. Notice that you receive the error message that is listed in the "Symptoms" section of this article.
  6. Open the first table, and then notice that the second table can now be opened.
Modification Type:MajorLast Reviewed:6/25/2004
Keywords:kbbug kbpending KB325835
©2004 Microsoft Corporation. All rights reserved.