Re: Help: Access 2.0 and Oracle7 problem

Crystal Report is also 16 bit (came with VB4 Pro16 bit)

I ran ODBCTest and got connected just fine. Looks like the problem lies with MS Access. Wonder if the Jet engine got anything to do with this?

paulj_at_sterlingcomp.co.uk (PJ) wrote:

>lh_at_earthlink.net wrote:
 

>>ENVIRONMENT:
>>
>>CLIENT:
>>Windows 95
>>MS Access 2.0
>>ODBC: Oracle7 1.11.0.5, 1.11.1.5
>>
>>SERVER:
>>SQL*Net SPX 1.1.8.0.0
>>SQL*Net TCP/IP 1.1.9.0.0
>>
>>After user name and password, MS Access returns the following error:
>>
>>[Microsoft][ODBC DLL]Driver's SQLSetConnectOption
>>failed(#0)[Oracle][ODBC Oracle Driver]Driver not capable.
>>(#0)[Oracle][ODBC Oracle Driver][Oracle OCI][ORA-12154:TNS:could not
>>resolve database name. [#12154]
>>
>>The same set up works fine in Crystal Report in the same environment.
>>Does Access 2.0 use anythign filter or engine ON TOP of Oracle ODBC
>>driver, thus causing the problem?
>>
>>
>Is Crystal Reports 32 Bit? If so, it could be using 32 bit ODBC which
>may have a different connect string to the 16 bit ODBC drivers used by
>Access 2.0.
 

>Worth a shot.
Received on Fri Jul 12 1996 - 00:00:00 CEST