Re: Can Oracle ODBC 16 and 32 bit exist on the same Machine?

Tim Nickason <tnickasn_at_rogers.wave.ca> wrote in article <01bcd079$e90e9b00$03727018_at_timmy.ns.bc.rogers.wave.ca>...
> Does anyone know if Oracle ODBC driver 2.x for win (16 bit) coexist at
> the same time as the win95 version (32 bit)?
>
> I have been able to install the win95 version and use it successfully,
 but
> not 16bit on the same machine.
> I keep getting an error in odbc admin that says the driver cant be loaded
> because of a lack of memory).

Both 16 and 32bit SQL*Net can coexist on a Win95 PC - therefore both 16 and 32bit ODBC should work across the respective SQL*Net drivers.

A few thing to keep in mind. 16bit to 32bit translation (thunking) in the above setup only works at the IP stack level, i.e. 16bit IP calls with be thunked to the 32bit IP stack and transmitted. That means that you still need both 16 and 32bit SQL*Net and ODBC drivers. The 16bit ODBC driver will call the 16bit SQL*Net whose IP sends and receives will be thunked to 32bit. Ditto for the 32bit ODBC and SQL*Net, except that there's no thunking involved.

When installing 16bit SQL*Net, make sure that it's not in the same directory as the 32bit Oracle software (c:\orawin as oppose to c:\orawin95), select the Windows for Workgroups VXD TCP/IP driver and add the c:\orawin\bin directory also to the path in order for Win95 to be able locate and load the 16bit Oracle DLLs when the ODBC driver requests it.

Oh yes, forgot to mention: that insufficient memory error by the ODBC administrator is crap. It gives that error because it can not locate the required DLL(s) that the ODBC driver requests. It wrongly assumes that the DLL(s) can not be loaded because there's insufficient memory. Yeah right - shows you what Microsoft thinks about their own memory model and memory management...

So make sure you have installed 16bit SQL*Net, and make sure you add the bin to the path - and try again. :-)

regards,
Billy Received on Mon Oct 06 1997 - 00:00:00 CDT