DOA 3.4.3 / 3.4.5 compatibility with Oracle 8.1.7

[hduque]

We began using DOA 3.4.3 for Oracle 8.1.6 access. No problem. But we changed to Oracle 8.1.7 and we've got troubles about "Access Violation". We now already have DOA 3.4.5 for using with Oracle 8.1.7. Are both version's compatible? Do I need anything else to make them work together?

 

[Marco Kalter]

Direct Oracle Access 3.4.x should work just fine with Oracle 8.1.7 and Net 8.1.7. In which module does the access violation occur? In your own executable, in a Net8 DLL, ...?

------------------
Marco Kalter
Allround Automations

 

[Dionbr]

I'm getting the same problem. The error in my case occurs when the program is closed or you use TOracleSession.Logoff.

If I got back to the 8.1.5 or 8.1.6 client it works ok. This happens on both my machines 1 WinNT4 SP6 and the other Win2K Sp2.

We are using DOA 3.4.5

Thanks

Dion

 

[Marco Kalter]

In which module does the access violation occur? In your own executable, in a Net8 DLL, ...?

------------------
Marco Kalter
Allround Automations

 

[franck barreaux]

Under W2K, in nt.dll!...

 

[Marco Kalter]

This is a Net8 DLL. Can you verify is SQL*Plus works correctly? If it does, can you use the Oracle Home Selector to make sure that the bin directory of the Primary Oracle Home is in the PATH environment variable (this is what the selector does)?

------------------
Marco Kalter
Allround Automations

 

[Anders]

I have the same problem. Access violation when closing my app (in ntdll.dll). I use WinNT4 sp6, Ora 8.1.7 and DOA 3.4.5.

/Anders Eriksson
Diveria AB

 

[ThomyKay]

I have the same problem within nt.dll (w2k, oracle8.1.7, doa3.4.5). It only occurs if you link doamonitor. However, must be solved!!!

 

[Gero]

Has anybody a solution to this problem?