>>>>

For what it may be worth. I inherited a Delphi BDE system with
similar problems and it turned out that there was a form linked (but
not used) which had a Database component on it. When the application
started, this component connected to Interbase and thus started a
transaction. Even though the primary database component (in a data
module) correctly used transactions, the hidden component kept a
transaction open indefinitely. This of course kept the OIT from
moving along.

>>>>

Thanks for the reply;



Is this possible/true even when the TDatabase connection uses a
SQLPASSTHRU MODE of SHARED AUTOCOMMIT? We understand this to mean that
the BDE manages all transaction boundaries.



All database components in the application must use a central TDatabase
component, as no BDE Alias is provided on end-user computers for the
InterBase database.



Also, all servers experiencing these problems are running on various
versions of Windows NT (4.x or 2K). We are now testing FireBird 1.0.2
on Red Hat Linux.



Thanks again.



Regards,



Hugh J Borst

hborst@...







[Non-text portions of this message have been removed]