Re: Linking with OCI for Windows NT and Windows 95

In article <01bbe626$9c166640$4625409b_at_puru-dell-mc>, pbalakrishnan_at_symantec.com says...
>
>Hello all,
>
>Is it true that to deploy an OCI application in both Windows NT and Windows
>95 clients, that the application be linked with two different sets of OCI
>libraries for Windows NT and Windows 95?
>
>Also, would an application linked with OCIW32.LIB (Oracle OCI 7.3) work
>with Oracle 7.1 SQLNet clients?
>
>I am a little bit confused with all the different OCI LIBRARY file names
>for the different versions of Oracle and would highly appreciate any input.
>
>Thanks.
>
>Puru Balakrishnan
>pbalakrishnan_at_symantec.com
>Symantec Corporation
>
>

Hi Puru,

I write shareware oci programs for Oracle developers (visit my home page, below!). My programs connect to different version of the oci client by dynamically attempting to load oci .dll files in a particular order with ociw32.dll at the head of the list. If you use a .lib file to link to oci, you are doing a static link as opposed to using loadlib to do a dynamic link. The ociw32.lib link library will connect your program to the ociw32.dll when you start up. If the client does not have ociw32.dll it will fail. OCIW32.DLL was written by Keith Majkut, Senior Software Engineer at Oracle. This dll dynamically loads the correct dll for the local oci libraries (Thanks Keith!)

So the answer is, you can use ociw32.lib to statically link ociw32.dll to your executable, but the client must have this dll! This dll was shipped with Oracle 7.2 and above. I'm not sure what the distribution rights are for this dll, you may just be able to include it with your program!

Good luck!

Mark Ford
Benthic Software
http://www.tiac.net/users/markford/index.htm Quality Oracle Shareware for Developers (Come See!) Received on Fri Dec 13 1996 - 00:00:00 CST