Hi all
I have a continuous form and I want to make it so that it does not update the underlying table until I click the Save button at the bottom of the form. That is, if the user makes a bunch of changes and then hits the cancel button, I want the table to be at the state it was before the form was opened. At the moment, it seems that moving from one field to the next in the continuous form saves the data.
I have tried to use Workspace's beginTrans method in the FormOpen event, with it's related CommitTrans and Rollback methods in the Click event for the Save and Cancel buttons respectively, but the behaviour is the same for both buttons - the new data gets posted to the table.
Is this a continuous form quirk, or am I not doing something right?
cheers
mcalex
I have a continuous form and I want to make it so that it does not update the underlying table until I click the Save button at the bottom of the form. That is, if the user makes a bunch of changes and then hits the cancel button, I want the table to be at the state it was before the form was opened. At the moment, it seems that moving from one field to the next in the continuous form saves the data.
I have tried to use Workspace's beginTrans method in the FormOpen event, with it's related CommitTrans and Rollback methods in the Click event for the Save and Cancel buttons respectively, but the behaviour is the same for both buttons - the new data gets posted to the table.
Is this a continuous form quirk, or am I not doing something right?
cheers
mcalex