New Tables & Queries Force me to Save As

[wrldruler]

I just took over a DB from the former developer.

I go to "Create query in Design View" or "Create table in Design
View". Do anything or nothing.

I try to close. It prompts me for a Save As, and won't let me close
until I give it a name and finish the Save As.

PITA. I can't build a temp query without having to save it. Then I
have to go and delete it. And if the query has a syntax error, the
Save As fails. I have to make the temp query valid, do the Save, then
delete. PITA.

Does anybody know what setting she changed that is forcing a Save As?

Thanks,

Chris

 

[Jeff Boyce]

Are you saying that you used to be able to create what you term a "temporary
query" without getting a Save As prompt?

I'm surprised! How would you expect Access to know the difference between a
new query that you planned to use only temporarily, and a new query that you
intended to use regularly thereafter?

I can imagine that you might not receive this warning/prompt if you turned
off the warnings (SetWarnings = No), but that would mean you would NEVER
know when something wrong was happening. Is that what you are after?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[John Spencer]

IF I recall correctly this is caused by warnings being set to false.
Try running
DoCmd.SetWarnings True
in the VBA immediate window.

When you attempt to close a changed/new query you should be get a save
dialog with Yes, No, and Cancel. If SetWarnings is false, the save
dialog will only have two choices for NEW queries and will automatically
save changes for existing queries.

Check out the options under tools to see if this is set permanently or
look for DoCmd.SetWarnings False in startup code, startup macro, or
other routines.

'====================================================
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
'====================================================

 

[wrldruler]

Yup, found it. In two spots she used "DoCmd.SetWarnings False" and
failed to follow it up by a "DoCmd.SetWarnings True". Fixed now.

PS: John, I graduated from UMBC in 2003 with a IFSM BA.

Thanks,

Chris