Implementing a Save, Delete or Cancel MsgBox

You need to use the Form_BeforeUpdate Event (of the
Subform) to ask the user whether to save or cancel the
Record currently being edited.

Check Access VB Help on the BeforeUpdate Event of a Form.

When the user moves the Focus from the Subform to the Main
Form, the Record (in the Subform) is also saved
automatically.

HTH
Van T. Dinh
MVP (Access)



-----Original Message-----
I have a subform embedded into a main form. It has some
buttons on it that
allow the user to enter a new record and decide whether
to save it or cancel
it (cmdNew, cmdSave, cmdCancel buttons). The problem is
that the user can
unfortunately do a number of other things that will
bypass the save and
cancel buttons:

1) Close the form.
2) Close the database.
3) Move to another record in the subform by the
navigation buttons.
4) Probably other ways that I haven't discovered.

Any of these things will cause the new record to be saved
probably without
the user realizing it thus allowing bad or incomplete
data into the
database.

How can I implement the sort of Save, Delete or Cancel
MsgBox seen on
Windows applications where before the application is
closed, the MsgBox
arises allowing the user to save or delete prior to
closing or actually
cancel the closing? I tried tying some code to the
OnUnload event but this
doesn't seem to work (the application closes or the form
closes
prematurely).

John


.

"TC" wrote in message
om...
"Arvin Meyer" wrote in message
...
"TC" wrote in message
...

Sure you can do it by not putting validation in BeforeUpdate events.
You
can
also do it by ensuring that there are never any records in the table.
Or
by
preventing the user from opening the application. Or by locking the PC
in
a
box so the user can not get to it.

My point - surely obvious to most readers - was that all of the usual
attempts to code a Cancel button are doomed to failure, because they
do
not
consider the focus issue that I described. I do not deny that this can
be
solved by ridiculous contortions such as removing all validation code
from
the very event that is designed for managing validation. In that
regard, I
agree that it is not "100% impossible". It is only 100% impossible for
people who like to do weird things such as using bound forms and/or
BeforeUpdate events for validations.


I don't want to argue the point

Neither do I - which is why I started to get heated.


so this will be my last post on the subject.

No point stopping if there is something worth discussing.


Simple Access front-end database applications are usually bound to the
data.
Most other applications are unbound. I prefer bound forms because they
are
easier to build and use ...

Agree 100%.


except under the condition that the edits are
cancellable. If the edits must be cancellable, there is little choice
but to
make unbound forms.

I don't see that. You simply tell your users to press the Esc key when
they want to cancel pending changes. This gives easy cancellation of
pending changes, while retaining the convenience of using bound forms
& having validation in BeforeUpdate events.


Experienced database developers should be comfortable
with both methods, as neither situation is unusual.


Cheers,
TC