You are correct that this is the mechanism used by extproc (i.e. each
pass loads/unloads the DLL). You can TRY using a LoadLibrary() call
(as an extproc) on the DLL in question to see if this will actually
increment the handle count and prevent the DLL from getting unloaded
when the extproc calls end. The only way this will work is if the
extproc is executing under the PID of the database process (rather
than it's own), but it is worth a try.
- call LoadLibrary() as an extproc on the DLL
- call your own external procedures on the DLL
- when done call FreeLibrary() as an extproc.
It may not work simply because the kernel may see extproc as a
distinct process and free the handles anyway when the process ends...
Received on Mon May 24 1999 - 11:33:39 CDT
