Article ID: 167239
Article Last Modified on 2/22/2005
APPLIES TO
- Microsoft Visual FoxPro 3.0 Standard Edition
- Microsoft Visual FoxPro 3.0b Standard Edition
- Microsoft Data Access Components 2.5
This article was previously published under Q167239
SYMPTOMS
When using the Oracle 7.3 ODBC Driver (version 1.15.0301) provided by Oracle Corporation to connect to an Oracle server, if an SQLExec() call encounters an error, the connection to the server is no longer valid. Issuing subsequent SQLExec() calls after a previous command has failed results in the following error:
RESOLUTION
This problem occurs only with the Oracle 7.3 ODBC driver provided by Oracle Corporation. Using the Visigenic Oracle ODBC Driver (version 2.00.0000) or the Microsoft Oracle ODBC Driver (version 2.00.006325) works correctly. This problem does not occur in Visual FoxPro version 5.0 or 5.0a.
NOTE: As of 12/9/98, Visigenic has been acquired by INPRISE, Inc.
For information about how to contact INPRISE, Inc., query in the Microsoft Knowledge Base for one of the following articles:
65416 Hardware and Software Third-Party Vendor Contact List, A-K
60781 Hardware and Software Third-Party Vendor Contact List, L-P
60782 Hardware and Software Third-Party Vendor Contact List, Q-Z
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This has been corrected in Visual FoxPro 6.0.
MORE INFORMATION
Steps to Reproduce Behavior
- Create an ODBC data source using the Oracle 7.3 ODBC driver.
Connect to this data source using the SQLConnect() function:
Handle=SQLConnect(<Oracle DSN>,<user id>,<password>)Send an invalid SQL statement to the Oracle server:
=SQLExec(Handle,"This is an invalid SQL command")- Send a valid SQL statement to the Oracle server.
The SQLExec function returns a -1 indicating an error.
Keywords: kbinterop kbprb KB167239
