Trailblazer
MIS
Rather than load ODBC on 200 networked clients (Win 97), we hoped to put ODBC on an NT server and have the clients' Access grab the ODBC stuff from the NT. Ran REGEDIT and updated the registry to (what I *think* are) the appropriate settings. Yet, whenever Access attempts to link to external tables (Oracle in this case), we get various ODBC errors, such as a no find on odbc32.dll (most commonly).<br>
<br>
As long as the ODBC is on the client, the Access processes work fine. If you remove the ODBC from the client and try to point Access to the NT server, it's a no go. All other connections work properly when odbc is not on the client (odbctest connects and returns data. SQL works too); the only uncooperative component is Access. Am I trying to do something that cannot be done? Is there a registry parameter that I'm overlooking? Do I need to re-setup Access? Or should I just surrender and install ODBC on every client?<br>
<br>
Thanks for any and all suggestions!
<br>
As long as the ODBC is on the client, the Access processes work fine. If you remove the ODBC from the client and try to point Access to the NT server, it's a no go. All other connections work properly when odbc is not on the client (odbctest connects and returns data. SQL works too); the only uncooperative component is Access. Am I trying to do something that cannot be done? Is there a registry parameter that I'm overlooking? Do I need to re-setup Access? Or should I just surrender and install ODBC on every client?<br>
<br>
Thanks for any and all suggestions!