Re:Must Hard Commit after Post ?
Ari Fikri writes:
Quote
Hi All,
Since using Hard Commit will close all connection in all IBX component,
while using Commit Retaining we're still risking of losing data when the
power goes
down, what policy must be taken to overcome this problem, when we're using
IB component ? If multiple forms are showing we're can not just hard commit
the dataset
because it will close all connection to the Database.
What we want to perform is permanently save the data to the DB while
maintaining
connection to the DB.
Thanks In Advance
Ari,
I really recommend using a separate TIBTransaction component on each of
your forms that hangs around, such as in an MDI application. That way
when you do a hard commit that requires you to re-open the datasets, the
effects are localized to that form/data module combo.
Also, I use ClientDataSets A LOT.
Lately I have discovered RemObjects and DataAbstract that allow me to
quickly create a middle tier (VCL Server) that still uses IBX (it's
faster than anything else as far as I can tell). They have this
DAClientDataTable that hooks up to any complex data set in your middle
tier. You can insert/edit/delete to your hearts content, then
ApplyUpdates and the middle tier takes care of all the transaction
issues. Your client stays open. I am migrating to this architecture as
fast as I can.
Loren Szendre