Is there a way to modify an external module DLL without stopping
server?

Tim, please consider a better a register/unregister mechanism for
external DLLs other than simply scan config path for new o deleted
DLLs. (It's just a suggestion)

If a DLL fails on load, how to find the cause of error (example,
missing BPL)?


Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.

Tiago,

<< Is there a way to modify an external module DLL without stopping server?
>>

If all sessions that are using the DLL are stopped, then you should be able
to modify the external module.

<< Tim, please consider a better a register/unregister mechanism for
external DLLs other than simply scan config path for new o deleted DLLs.
(It's just a suggestion) >>

The registration mechanism is when you use the external module with a
function/procedure.  Otherwise, the DLL is simply ignored.  Besides,
unregistering the DLL won't help you here because we wouldn't allow you to
unregister a DLL that is in use by a session, so you would still have to
make sure that all sessions that are using the module are removed from the
EDB Server.

<< If a DLL fails on load, how to find the cause of error (example, missing
BPL)? >>

For now you'll have to pop it into the debugger.  I'll see about adding a
logged error to the configuration log for this.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

>If all sessions that are using the DLL are stopped, then you should be able
>to modify the external module.
Ok, I'll check this.

>For now you'll have to pop it into the debugger.  I'll see about adding a
>logged error to the configuration log for this.

Trapping a.v. and other unspected errors in DLL would be appreciated
in development phase.

Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.