Re: Linking with OCI Libraries

From: Keith Majkut <kmajkut_at_netcom.com>
Date: 1996/12/10
Message-ID: <kmajkutE26D1D.KvM_at_netcom.com>#1/1


In article <01bbe626$c41b4d90$4625409b_at_puru-dell-mc>, Puru Balakrishnan <pbalakrishnan_at_symantec.com> wrote:
>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?
 Not any more.
>
>Also, would an application linked with OCIW32.LIB (Oracle OCI 7.3) work
>with Oracle 7.1 SQLNet clients?
 Yes.
>
>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.
ok, here's the deal.
Oracle renames the client lib/dll ORA*.DLL for each version. This became a hassle so starting with 7.2 OCIW32.LIB/DLL were released. This DLL will dynamically load whichever Oracle DLL it find.(Calls LoadLibrary and GetProcAddress). It is a loading layer only, do the other ORA*.DLL files must still be around. It does mean that you don't have to keep relinking.

OCIW32 doesn't help if you developed using a 7.3 function but the user you sent it to only has 7.2. Again, it only dynamically loads the client dll.

Finally, you may have been told there are different versions of the client libs for 95/NT. There are not. There used to be NT only versions for Oracle 7.1 and previous. Why? Because Win95 didn't exist when those libs were built.

Also, the names of the client dlls(if you wanted to link directly to them, are ORA7*.LIB/DLL starting with 7.2. Some for 95/NT.

>
>Thanks.
>
>Puru Balakrishnan
>pbalakrishnan_at_symantec.com
>Symantec Corporation
>
Received on Tue Dec 10 1996 - 00:00:00 CET

Original text of this message