Wanting SetWarnings set to true

[Guest]

Whether using DoCmd.SetWarnings True or SetWarnings Yes action, I can't get
the warnings to display. Just trying to create simple close button that will
not save if the answer to the prompt is no, but program always saves without
prompting. Have been searching for a setting also, with no luck.

 

[Rick Brandt]

Whether using DoCmd.SetWarnings True or SetWarnings Yes action, I
can't get the warnings to display. Just trying to create simple close
button that will not save if the answer to the prompt is no, but
program always saves without prompting. Have been searching for a
setting also, with no luck.

There is no built in warning for saving a reocrd. If you want one (bad idea
IMO) then you have to add your own in the BeforeUpdate event of the form.

If MsgBox("Save?",vbYesNo) = VbNo Then
Cancel =True
Me.Undo
End If

 

[Jon Lewis]

What's your rational for thinking that a save record warning is a bad idea?
Just interested.

Jon Lewis

 

[Rick Brandt]

What's your rational for thinking that a save record warning is a bad idea?
Just interested.

I just don't follow the logic that users will expend effort to create or modify
records only to decide (oh well, never mind, I was just honing my typing
skills). If they don't want to change a record then they won't.

On those rare occasions where the user will decide that they don't want to save
changes why would a "Do you want to save?" be necessary? Won't they know
whether they want to save before such a prompt comes up?

Also, to maintain consistency one would have to add these silly prompts to EVERY
Access form created. If a user is exposed to one form that doesn't save without
a warning then they will expect that this is the normal way Access works and
then be surprised when they encounter a form that doesn't prompt them. Do you
really want to add this "feature" to every form you will ever create in all your
apps?

 

[Jon Lewis]

Well I'm not convinced! What about inadvertent keystrokes deleting
information from a field for example?

 

[Rick Brandt]

Well I'm not convinced! What about inadvertent keystrokes deleting
information from a field for example?

If the user realizes they did that they just press <Escape> to undo those
changes. If they don't realize it then I fail to see how a prompt is going
to help.