Delay commit on a bound form?

[robert.waters]

Typically when you first enter data in any bound control on a bound
form, a new record is created; is there any way for me to delay this
process, for instance until a button is pressed? I don't want to use
any funky undo magic.

Thanks!

 

[Rick Brandt]

Typically when you first enter data in any bound control on a bound
form, a new record is created; is there any way for me to delay this
process, for instance until a button is pressed? I don't want to use
any funky undo magic.

Thanks!

Correction. A new record is "started". It won't be "created" until it is
saved. Undo is all you have I'm afraid.

 

[ruralguy via AccessMonster.com]

You wouldn't be using an AutoNumber field for something beside a unique
number would you?

 

[robert.waters]

You wouldn't be using an AutoNumber field for something beside a unique
number would you?

Ha. No, but I know why you asked; it does annoy me that records that
are 'started' consume an autonumber, even if the record is unused.

My problem is that I have a high-usage bound form that is constantly
being 'cancelled', and I thought it would make more sense to not even
create the record until the user is sure they want to save it. I
guess I could just change it to an unbound form, but that would take
work

Thanks for all your help, folks.

 

[ruralguy via AccessMonster.com]

Thanks for the reply. Good luck with the project.

 

[Bob Quintal]

Ha. No, but I know why you asked; it does annoy me that
records that are 'started' consume an autonumber, even if the
record is unused.

My problem is that I have a high-usage bound form that is
constantly being 'cancelled', and I thought it would make more
sense to not even create the record until the user is sure
they want to save it. I guess I could just change it to an
unbound form, but that would take work

Thanks for all your help, folks.

The record is only saved when 1. the user changes to another
record, 2. manually saves the record via the menu bar. or 3.
closes the form.

I usually handle controlling saves by putting a messagebox in
the form's before update event, that asks the user if he wants
to save, and either lets the process continue if yes, or
executes a me.undo statement then closes the form.