ODBC-connection to '' failed

[allidap]

Greetings!

Newbie to this site and group. My apology if this is an issues that has been discussed.

We're in the process of transitioning Access DB -> SQL Server. This in itself isn't a real problem. What is... Linked tables!

Scenario... Access DB A, B and C. DB A and B have a linked table to DB C. Each DB has it's own respective application. For all intents and purposes, when migrated to SQL, the databases will be seperated as well.

I've moved DB C to SQL and do not have a problem. I've changed the respective application to point the SQL DB and all is well.

I then created ODBC connections for the table in Access DB A and B to point to the SQL Server DB. All is well. I can open the Access DB and open the table and get results. BUT...

When I use the respective applications for DB A and B, there is an ODBC--connection to '' failed. Don't quite understand why and how to resolve. The respective applications use an ODBC connection to communicate with their respective DB. Is this the problem? ODBC attempting to connect to another ODBC?

Any input on this topic will be greatly appreciated.

Thanks!!!

 

[ssatech]

Don't understand what you mean?
"I then created ODBC connections for the table in Access DB A and B to point to the SQL Server DB. All is well. I can open the Access DB and open the table and get results."

If you can see the tables, whats the problem?
Are you getting "ODBC--connection to "failed" when you are running Forms?

 

[jsteph]

I vaguely recall something to do with the table-naming or index usage, or data-type anomolies when this error happens.

Do you get this error when accessing certain tables, or any/all tables? Can you open the tables in datasheet view but this error happens in some code module?
--Jim

 

[allidap]

TO address the first response at 7:21, all is well when I open the table in Access. When I open the first Access DB (A) and open the table that is linked to the SQL Server DB table, all of the data is retrieved and accessible. The same goes for the table in the second Access DB (B).

The problem occurs when I use the application that interacts with the Access DB A and B and the table that is linked to the SQL Server DB table.

The problem is just in referencing the Access DB table that is linked to a SQL Server DB table from within a VB application. Referencing all other tables in the same Access DB from the VB application works without incident.

-Bob