Re: Oracle window DLLs (how to close them?)

In article <3nr6qt$l4t_at_ixnews3.ix.netcom.com> cox2_at_ix.netcom.com (Guy Cox) writes:
>From: cox2_at_ix.netcom.com (Guy Cox)
>Subject: Re: Oracle window DLLs (how to close them?)
>Date: 28 Apr 1995 16:58:05 GMT
 

>In <3nqspr$pba_at_lucy.infi.net> gtravis_at_richmond.infi.net (Glenn Travis) writes:
 

>>
>>Is there a parameter in the oracle.ini file in windows to close the
>>Oracle dlls (specifically mwinsock.dll, winsock.dll, sql*.dll) when
>>closing a windows app using slqnet to Oracle connections?
>>
>>It appears that when you access an Oracle database using SQL*Net from
>>Windows and/or ODBC (or not) - then close the app, Oracle leaves the dlls
>>open in windows. Powerbuilder does this too, in assuming that you will
>>use the app again in the near future and it won't have to re-open the
>>libs, and it becomes quicker.
>>

I've only seen this with PB, CDE2 seems to clean them all out unless you have pre-loaded them with cdeinit. I think it's a PB prob.

>>I want the

libs closed and don't want to have to exit and restart windows >>to get a clean environment every time. Anybody know why they do this and >>how to stop it.>>
>>(I know Ingres has a line in a config file on the PC to unload the libs
>>on exit.)
>>
>>thanks,
>>--
>>Glenn Travis
>>DBA
>>Circuit City Stores, Inc.
>>Richmond, VA USA
>>gtravis_at_richmond.infi.net
>>gtravis_at_aol.com
>>
>>
>There are several DLL killers around. They must be used with caution. Check the
>archives at CICA or possibly the gopher/ftp site at Microsoft.
Received on Mon May 01 1995 - 00:00:00 CEST