🚀 go-pugleaf

Hi, Clayton!

Each .exe definitely gets its own session (the default TSession
"Session"). Each thread must have a separate session. Since a DLL gets
its own application and the Session is Application based, I suspect this
means the same for the DLL. The exception, I believe is packages, where
all packages share the application object of the using application (I
think).

Good luck!

----


Clayton wrote:

I haven't tried using a session other than the default session yet.
Does
each EXE and DLL gets its own default session object then?

Yes, I plan on the DLL doing all the management.  I have several classes
and
objects that will return the items I need in TList's or TStringList's or

just plain record objects.

The dynamically loaded DLL has already been given the main executable's
TApplication object and is using it.  Does an implicitly loaded DLL have
a
different TApplication object?  (I guess I could write a little test to
see
if that's the case).

So I'll try setting all application objects the same and then create my
own
session object for the database DLL.

Thanks for the direction,

Clayton


--
------
Mark Cashman (TeamB - C++ Builder), creator of The Temporal Doorway at
http://www.temporaldoorway.com
- Original digital art, writing, music and more -
C++ Builder / JBuilder Tips and The C++ Builder Programmer's Webring
(Join us!)
http://www.temporaldoorway.com/programming/index.htm
------