All,

Several weeks ago, I posted an issue where I was losing data after our application hung during a database operation. Unfortunately, after updating all of my clients to released version FB1.5, it's still happening. Here's the scenario:

: During a database operation, the system hangs
: The user uses Ctrl+Alt+Del to kill the process and restarts the app
: All subsequent database operations are never posted to the database

The only way to cure the problem is to reboot the computer. Unfortunately, this is an extreme measure and is unacceptable to our clientele. Sometimes, without realizing it, hundreds of transactions are lost.

I have debugged our application thoroughly and am very certain that the application itself doesn't leave any open transactions so it's not an issue of not commiting. After much heartache, I believe that the problem lies in FBClient.dll.

Has anyone else experienced this problem?
Is there any way to send FBClient a message to force commit all pending transactions?
Is there a way I can make sure that FBClient isn't still loaded when I start my application? If it is loaded, is there any way to tell it to unload?

I am using Delphi 5 and IBX. This is happening on many clients computers across the country on all flavors of Windows. The date of GDS32.dll and FBClient.DLL is 2/23/2004.

Any help would be greatly appreciated.

Thanks,

-Ed Salgado
www.OneDomain.com
ed@...
TV Media Software

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