Subject | FB Processes in Windows Classic 1.5.2 |
---|---|
Author | ian.billups@incerts.co.uk |
Post date | 2005-10-20T16:53:04Z |
Hi All,
Could someone help me, please, to understand exactly when new processes
start and old processes die when we use FB Classic 1.5.2 for Windows.
We did a small experiment--we wrote a small .NET application using
DataAdapters. It opens a connection to FB and closes it. A new FB
process starts, but it does not die when the connection closes. It dies
when the *application* closes.
So, there is one FB process in Windows per *application*. Is there some
way that an application can make the FB process die whilst it continues
to run itself? I mean, can an application close the FB process
programmatically?
Many thanks,
Ian.
Could someone help me, please, to understand exactly when new processes
start and old processes die when we use FB Classic 1.5.2 for Windows.
We did a small experiment--we wrote a small .NET application using
DataAdapters. It opens a connection to FB and closes it. A new FB
process starts, but it does not die when the connection closes. It dies
when the *application* closes.
So, there is one FB process in Windows per *application*. Is there some
way that an application can make the FB process die whilst it continues
to run itself? I mean, can an application close the FB process
programmatically?
Many thanks,
Ian.