Is there a way to exit an Access database WITHOUT saving changes?

[Guest]

HELP!!! I inadvertently starting entering data into a form before I selected
a blank record. I overwrote 2 records before I realized it. I was able to
use the "undo saved record" option for the second record, but I could not
undo the first overwrite. Is there any way I can exit the database WITHOUT
saving my changes? (I can't believe I did that)!

Thanks!

Lori

 

[Roger Carlson]

No. Changes are saved each time you move from one record to the next.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[Guest]

Probably not. Unless using something fancy like an unbound form, once you
move from one record to another either at form, query, or table level, that
record is saved. You could try tapping the Esc key on the keyboard but I
really doubt that it will help.

Do you have a recent backup? You might be able to find the old record there
and re-enter it.

 

[Guest]

Thank you Roger & Jerry! (That's what I was afraid of. I went ahead &
called our IS group to have them re-load yesterday's version from the
backup). Ugh that was so dumb! Auto save is a great thing (until you pull a
"Lori").

Have a good one guys!

Lori

 

[Guest]

Pull a "Lori"? I thought the phrase was "Pull a Jerry". If I only could
learn from my mistakes, I'd be very, very wise indeed.

If this becomes a problem, you could open the form in Data Entry mode.

 

[Roger Carlson]

Good thought, Jerry. Another is to have the form open to the New Record.
Create an event procedure for the OnOpen event with the following code.

Private Sub Form_Open(Cancel As Integer)
DoCmd.GoToRecord , , acNewRec
End Sub

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[Guest]

This is a prime example of why a MODAL user interface is desirable. It has
become fashionable recently to tout MODELESS interfaces - ie. the user can do
anything at anytime. You would have been spared the grief if the form had
been set to disallow edits/additions, and you had to click on some button to
either enter a new record or change the current one - ie. consciously switch
from viewing mode to edit mode or entry mode. Makes for much more robust
databases.

 

[Guest]

You can also create a sub or functino that is called averytime the user tries
to enter data in a form. The function will display a "YesNo"-like msgbox with
text prompt "Are u sure u want to edit the record?". This is one more
"security level".
John