Form Transaction Processing

[soniqantranig]

End-users would like the startup form to behave much like Excel as far as saving the data being inputted i.e. they'd like to go ahead and modify the data but be able to commit the modifications only when they're ready to with a "Save" button or something of the sort, otherwise the data would remain unchanged.
Any suggestions?

[TonyES]

One of the option would be to create a copy of the Prevision table, and to bind the form to a query based on the copy instead of the original. When the user clicks Save, transfer the records to the original table. And the other option would be to create an unbound version of the form, but that would be a lot of work. For an unbound form, you'd have to create a text box for each field and for each of the 24 hours of the day - an unbound form by definition is not a continuous form, so you must simulate it. You don't necessarily need After Update event procedures for the controls. When the form is opened to edit existing records, you'd use ADO or DAO code to open a record set, then loop through its records and fields to populate the controls on the form. The Save command button would use ADO or DAO code to add new records or update existing records, as appropriate. The Cancel command button would simply close the form. BeginTrans etc. can be used if you want to roll back the entire save operation if an error occurs.

[soniqantranig]

Thank you for replying.

[Justin88]

Yah to be honest thats quite true