""Don Gollahon"" <gollahon@...> wrote in message
news:CPEBLJABNFKGGBCHNFBMCEFICHAA.gollahon@......

>
> Note: most of the time this happens when one of the users exits our app.

I

> have checked and rechecked our transactions to make sure they are all
> commited regularly (every 200 records for our batch jobs which is most of
> what we do in-house on IB) and all looks fine to me.

Not sure about all the benefit of doing regular commits with swep interval
set to zero, but if you don't use events, the only thing to check is what
does IBX when it disconnects. Does it do some rollback of internal queries,
for example?

Unfortunately, as you can have a reproducible case, facts turn really tricky
to be discovered.

An extreme solution would be: install the debug version of the engine with
the sources available, then use MSDEV to attach to the live process, break
it and use the "step" command in the debugger so it prompts you for the
source file while trying to debug step-wise, then direct the debugger to the
proper location and you'll see the offending code. Also, you can change
debugger between threads as expected. You could do that in your local
machine.

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing