C
Corey-g via AccessMonster.com
Hi All,
I am linking Oracle tables to my A2K3 FE, which seemed to be working fine.
But now that I'm trying to implement some fancy code to check if the tables
exist, relink, etc... I have found something strange I was hoping somebody
else could explain.
It seems that I can create an ADO connection to the Oracle BE using "OraOLEDB.
Oracle" as the provider string, and I can execute queries and see results.
But when I'm trying to link the tables using DAO I get an ODBC Call Failed
error (3146). If I change the provider string to "{Oralce in XE}" then it
works fine.
So I'm guessing that I can use the driver name in ADO, but I need to use the
DSN name for DAO. Only issue is that I'm trying to do this DSN-Less.
Hope that's clear and someone knows what I'm talking about,
Corey
I am linking Oracle tables to my A2K3 FE, which seemed to be working fine.
But now that I'm trying to implement some fancy code to check if the tables
exist, relink, etc... I have found something strange I was hoping somebody
else could explain.
It seems that I can create an ADO connection to the Oracle BE using "OraOLEDB.
Oracle" as the provider string, and I can execute queries and see results.
But when I'm trying to link the tables using DAO I get an ODBC Call Failed
error (3146). If I change the provider string to "{Oralce in XE}" then it
works fine.
So I'm guessing that I can use the driver name in ADO, but I need to use the
DSN name for DAO. Only issue is that I'm trying to do this DSN-Less.
Hope that's clear and someone knows what I'm talking about,
Corey