Hi Helen,

"Helen Borrie" <helebor@...> wrote in message
news:5.1.0.14.0.20020107203933.05c35360@......

> At 09:27 AM 07-01-02 +0100, you wrote:
>
> >So, one TIB_Session _per_ TIB_Connection? And then the session
> >component has to be destroyed when the connection is destroyed?
> >
>
> Martijn,
> Actually, it's one TIB_Session per module. So if you have a module (e.g.

application) that has two or more connections, you still have just one
session component. But a DLL is a separate module so it needs its own
session component...same if you have a modulized application architecture
like we used to do in Delphi 1, one session per module...

>
> The IB_Session needs to be the first thing created in your module, too;

and it will be the last thing destroyed when the library object destroys
stuff.

>

I have a single application - with no IBO whatsoever. This application loads
a DLL with the IBO code. The application then requests objects (cursors,
connections etc) from the DLL and uses them. The application can request
multiple connections (TIB_Connection) and multiple queries. All in a single
thread (for now).

So one TIB_Session in the DLL should be enough then...

--
Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."