At 11:22 PM 24/10/2007, you wrote:

>> Maybe your the problem does not relly on populating the CDS (as far as
>> everything is working as should) but rather on some editing/updating
>> process -- have you checked those?? mainly the master-details updating.
>
>As you probably know, DBX should take care of everything. It doesn't
>even have a Transaction component like IBX.

Oh, but it does. It doesn't have a *separate* transaction component. It has a transaction wrapper embedded in TSQLConnection. The TSQLConnection methods BeginTransaction, Commit and Rollback operate on that transaction (not on the connection); and you test the state of that transaction using the InTransaction property.

No more Delphi lessons. This isn't a Delphi forum. Read the help for DBX.

>So how can I check if it's leaving some transactions open?

Ummm. gstat -h, where this all began. ;-) (Why your sweep wasn't moving the OIT forward...stuck OIT....long-running transaction....di-da-di-di)

./heLen


./heLen