>>>I'm having a strange behavior with VFP9sp2
>>>
>>>Using VFP front end to communicate with Oracle 9i database
>>>
>>>When creating DSN in ODBC32, connection is successfull with both ORACLE ODBC driver is 9.02 and Microsoft for Oracle 6.01.7601.19135
>>>
>>>When compiling VFP EXE. The Application works! It connects to Oracle.
>>>
>>>Here is the weird part....
>>>
>>>When running the app within VFP9, the ODBC dialog appear asking for password and every time it fails to give a handle
>>>
>>>I've tried SQLConnect() and SQLStringConnect(), same behavior with both OCBC32 drivers.
>>>
>>>So, I'm unable to debug and every time I want to test I need to compile.
>>>
>>>Any Clue how to resolve this odd behavior?
>>
>>With ODBC errors, AERROR( ) usually contains information useful for debugging. If you call it after an ODBC error, you can view the contents of the array, write the contents out to a file with STRTOFILE( ) etc.
>
>The AERROR( ) is : "Connectivity error: [Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve service name
>But it is not true, it Works if compiled or going with the ODBC interface or with TOAD...
There are some useful-looking hits if you Google [ORA-12154: TNS:could not resolve service name].
With an ODBC error there are usually 4 or 5 rows in AERROR( ). Could you post them all, verbatim?
An excellent resource for connection strings is
http://www.connectionstrings.com . You can check that you have all required/recommended parameters in your strings. Also check that you don't have any typos in the parameters.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up