Subject | Re: [firebird-support] Understanding Sweep |
---|---|
Author | Anderson Farias |
Post date | 2007-10-24T12:49:18Z |
Hi,
far as one have setup everything fine (and with DBX is probably most
out-of-the-box) populating a CDS it's just open it!
The provider will take care of starting a transaction, executing the query,
fetch records and send to CDS and then commit the transaction.
There are of course som 'tricks' (using it with IBX at least) like the
transaction associated to the query component can not be already started,
and some others.
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.
Regards,
Anderson
> I'm familiar with TSQLConnection and its methods to handleI don't use DBX but use CDS+Provider+IBX and it's pretty much the case. As
> transactions, but I don't see how should you it when populating a
> ClientDataset. To populate a ClientDataset I just "open" it.
far as one have setup everything fine (and with DBX is probably most
out-of-the-box) populating a CDS it's just open it!
The provider will take care of starting a transaction, executing the query,
fetch records and send to CDS and then commit the transaction.
There are of course som 'tricks' (using it with IBX at least) like the
transaction associated to the query component can not be already started,
and some others.
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.
Regards,
Anderson