CPU Window - Oracle Instant Client - ODAC
Posted: Thu 15 Feb 2007 16:51
Hi all.
I get a CPU Window at runtime using Oracle Instant Client and the latest release of ODAC available with Delphi 5 projects at runtime.
The configuration is:
- MS Windows 2000 SP4 (5.00.2195)
- 10.2.0.3 Oracle Instant Client
- \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\TNS_ADMIN or TNS_ADMIN environment variable to let the OIC know where the .ora files are located (same effects)
- Delphi 5 update pack 1 (all updates installed)
- ODAC 5.80.0.39 just downloaded and installed
- new project without "Build with runtime packages" checked
- on the Form, just a TOraSession component with a valid ConnectString and a button with the following code:
OraSession1.Connected := false ;
OraSession1.Connected := true ;
There is a different behaviour between these situations:
- if the Connected property of the TOraSession is set to True at design time, then at runtime, when the containing Form is created, the connection becomes active and following reconnections are error free (using the button);
- if the Connected property of the TOraSession is set to False at design time, when the button is pressed at runtime, I get a CPU Window with current address near ntDll.DbgUserBreakPoint.
Perhaps there could be a different initialization of the OCI's.
Thanks a lot for your kind support.
Sandro
I get a CPU Window at runtime using Oracle Instant Client and the latest release of ODAC available with Delphi 5 projects at runtime.
The configuration is:
- MS Windows 2000 SP4 (5.00.2195)
- 10.2.0.3 Oracle Instant Client
- \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\TNS_ADMIN or TNS_ADMIN environment variable to let the OIC know where the .ora files are located (same effects)
- Delphi 5 update pack 1 (all updates installed)
- ODAC 5.80.0.39 just downloaded and installed
- new project without "Build with runtime packages" checked
- on the Form, just a TOraSession component with a valid ConnectString and a button with the following code:
OraSession1.Connected := false ;
OraSession1.Connected := true ;
There is a different behaviour between these situations:
- if the Connected property of the TOraSession is set to True at design time, then at runtime, when the containing Form is created, the connection becomes active and following reconnections are error free (using the button);
- if the Connected property of the TOraSession is set to False at design time, when the button is pressed at runtime, I get a CPU Window with current address near ntDll.DbgUserBreakPoint.
Perhaps there could be a different initialization of the OCI's.
Thanks a lot for your kind support.
Sandro