Roy,

<< You are but a) I'll forgive you and b) continue to ignore you >>



<< There's only one external function (and only one external dll) involved
in the triggers and opening any one of the tables seems to "solve" the
problem.

Do I need to do this per function, per dll, per database or what? >>

Per session.

<< Would it be a silly suggestion to ask for a function to say LoadAndBind
these functions for these databases? >>

See my response to Barry for the rationale behind the dynamic
loading/unloading.  I could probably add an engine option to tell the engine
to load all modules at session startup, especially now that the modules are
specifically "created" and present in the configuration.

Tim Young
Elevate Software
www.elevatesoft.com

Tim

>Per session.

Brill. I'll set up an in-memory table which access everything in site and just leave it sitting there open.

><< Would it be a silly suggestion to ask for a function to say LoadAndBind
>these functions for these databases? >>
>
>See my response to Barry for the rationale behind the dynamic
>loading/unloading. I could probably add an engine option to tell the engine
>to load all modules at session startup, especially now that the modules are
>specifically "created" and present in the configuration.

I for one would be happy to take the hit associated with loading when the app starts rather than at the first call.

Thanks

Roy

<I for one would be happy to take the hit associated with loading when the app starts rather than at the first call.>

+1

Barry