From: Mark on
For me the fix was to re-enable warnings; VBA code in my database applied the following command:

DoCmd.Setwarnings False

I believe if you interrupt code after this command and before the setwarnings are re-enabled, that the warnings will remain off for all database objects.



Dave wrote:

Why does Access 2007 save query changes w/o prompting?
10-Sep-08

In some of my databases, when I edit a query in design mode Access saves the
changes I made without prompting me if I wish to save changes. Additionally
in those databases, it will force me to name and save a new query before I
can close the query or the database (clicking cancel will take me back to the
query pane w/o closing it).

I need to be able to run quick variants of existing queries or wholly new
queries, and look at the resulting data just that one time??? without having to
clean up a mess of temporary queries saved to my database, and without
breaking my existing queries because changes were saved without warning.

This only seems to happen on new databases that I create. When opening old
databases (created with Access 2000) it does not do this. Note that my new
databases are being saved Access 2000 file format to that they are compatible
with coworkers who have not upgraded to the latest access.

Previous Posts In This Thread:

On Wednesday, September 10, 2008 10:06 AM
Dave wrote:

Why does Access 2007 save query changes w/o prompting?
In some of my databases, when I edit a query in design mode Access saves the
changes I made without prompting me if I wish to save changes. Additionally
in those databases, it will force me to name and save a new query before I
can close the query or the database (clicking cancel will take me back to the
query pane w/o closing it).

I need to be able to run quick variants of existing queries or wholly new
queries, and look at the resulting data just that one time??? without having to
clean up a mess of temporary queries saved to my database, and without
breaking my existing queries because changes were saved without warning.

This only seems to happen on new databases that I create. When opening old
databases (created with Access 2000) it does not do this. Note that my new
databases are being saved Access 2000 file format to that they are compatible
with coworkers who have not upgraded to the latest access.


Submitted via EggHeadCafe - Software Developer Portal of Choice
Join Lists with LINQ - SharePoint 2010
http://www.eggheadcafe.com/tutorials/aspnet/b0c1cd0d-fe82-444e-a16e-7d3fb7d38eca/join-lists-with-linq--sh.aspx