Commit changes wiith DBEdit

[SymbolicFrank]

The easiest way to discard all changes at the end is by using TSQLTransaction.Rollback.

[rvk]

The easiest way to discard all changes at the end is by using TSQLTransaction.Rollback.

That would be fine if the TDbf (which Edson, TS, uses) has a transaction-facility, but it doesn't.

[Edson]

I'm agreed with rvk. DBGrid is not the place to do this. I created a small demo for using DBEdits and Edits in a configdialog with the buttons you want. I hope it helps.

Thanks @mangakissa, I'm going to study your code.    I think it will be very instructive.

But I'm afraid, I need to modify a complete table (no only a row) and then, have the ability to discard or save all the changes.

[rvk]

But I'm afraid, I need to modify a complete table (no only a row) and then, have the ability to discard or save all the changes.

I think the only option you have left, in that case, is using a TStringGrid (with goEditing in the Options). You can populate the StringGrid when entering the form en when the user wants to save the options you can write the rows to the database again.

[Edson]

Yes. That's the way. Actually I'm following the same scheme I've used in my ConfigFrame library:

Code: Pascal  [Select][+][-]

1.  +-----------+                  +-------------+                 +------------+
2.  |           | ReadDBToProp()   |             |  PropToWindow() |            |
3.  |           | ---------------> |             | --------------> |            |
4.  |   DB      |                  | Properties  |                 |    Form    |
5.  |           | SavePropToDB()   |             |  WindowToProp() |            |
6.  |           | <--------------- |             | <-------------- |            |
7.  +-----------+                  +-------------+                 +------------+
8.  

[mangakissa]

That's easy to to use. But if you still want use a datalayer like DBGrid, memdataset or bufdataset is your answer. Offcourse you can build an own class to hold the properties of your form.