how do I turn off autosave in design view...?

  • Thread starter Thread starter Kelvin Beaton
  • Start date Start date
K

Kelvin Beaton

Every to soften when I'm using Access (2003) it seems to get in a mode of
not prompting me if I want to save my changes.
This is very annoying when I'm testing and I make changes but I don't want
to save them.
Normally I make changes, then decide I don't want to save them, and close
the query, and NO when it asks if I want to save my changes...


Anyone else run into this?

Rebooting I think returns it to its state where it will ask if I want to
save changes...
I did open Note Pad and added text and when I closed it, it asked if I
wanted to save changes.

So it seem to only be an issue in Access...

Any input would be appreciated.

Kelvin
 
Also, I created a new query to so some testing with and went to close it and
it only gives me the option to Cancel the save or OK to save it.
The option is not there to say NO...

I rebooted and it seemed ok for a few minutes and then now it's
automatically saving...

HELP!

Thanks

Kelvin
 
Rebooting will not change this.

Likely, you have some code that executes

docmd.SetWarnings false

some code goes here

docmd.SetWarmings True

If your code stops, or you forgot to set warnings back on, then you get the
behaviours you describe.

I as a habit AVOID using SetWarnings in code, as usually you do NOT need to
do this.

Go to the debug window, and type in:

docmd.SetWarnings True

I believe there is a way of setting this in the tools->options menu..but, I
can't find it right now...

so, it your "open ended" code use of setwarnigns that is causing this
problem. So a global search on your code, and search for setwarnings......
 
Thanks for the reply.

I suspect you are correct....

Would you give me an example of how to NOT use SetWarnings?
I us SetWarnings to delete tables, overwrite tables etc...

Thanks for your help!!!

Kelvin
 
Kelvin Beaton said:
Thanks for the reply.

I suspect you are correct....

Would you give me an example of how to NOT use SetWarnings?
I us SetWarnings to delete tables, overwrite tables etc...

Thanks for your help!!!

Kelvin
Click to expand...

Yes.

To update a table, we go

currentdb.Execute strMySql,dbFailOnError

to delete table, we go

currentdb.Execute "drop table tblTempData",dbFailOnError

It been very many years since I used setwarmings.

You likely been using the docmd.runSql, and that more of a support for macro
code, then it is for writing vba code....

You can use setwramings, but it extra code, is a hassle if you forget to
turn them back on, and further, you better off to use the current connection
object, as some queries are NOT wrapped in a transaction (so, they run MUCH
faster). Note that you don't get the prompts like "you are about to update
bla bla bla...do you "really" want to do this".

So, use caution...as when you use the "execute" method, it does not wrap
things in a transaction, and does NOT give you the chance to bail out (but,
as mentioned, if you don't need that ability..then execute is considerably
faster in some cases).
 
you should always leave 'SetWarnings' on

and use Visual Source Safe
and Access Data Projects, while we're at it
 
S u s i e D B A said:
you should always leave 'SetWarnings' on

and use Visual Source Safe
and Access Data Projects, while we're at it
Click to expand...

Note that this person is really A a r o n K e m p f and that he is not an employee
of Microsoft.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Thanks Albert

I realize now that I see you options, that I am usually deleting or
overwriting local tables. Ones that I setup temporarly for reports and
such... I'm guessing your options are really only for SQL tables, correct?

On the other hand, maybe I should look at making them SQL tables, but I'd
lean towards that being over kill...
I'll look further into this, thanks for your input. Alway good to be
stretched a little...

Kelvin
 
I realize now that I see you options, that I am usually deleting or
overwriting local tables. Ones that I setup temporarly for reports and
such... I'm guessing your options are really only for SQL tables, correct?
Click to expand...

Ummmm....

You *DO* know that it is not necessary to create a table in order to generate
a Report, I hope? You can (and usually should) base a Report directly on a
Select query. It is NOT necessary to take the extra step of turning that
Select query into a MakeTable query!

John W. Vinson [MVP]
 
Kelvin Beaton said:
Thanks Albert

I realize now that I see you options, that I am usually deleting or
overwriting local tables. Ones that I setup temporarly for reports and
such... I'm guessing your options are really only for SQL tables, correct?
Click to expand...

Well, I always considered all tables in a mdb application sql tables.

You might want to show a small code snippet, or what kinds of code you are
running that is giving you those prompts.
On the other hand, maybe I should look at making them SQL tables, but I'd
lean towards that being over kill...
I'll look further into this, thanks for your input. Alway good to be
stretched a little...
Click to expand...


I don't really understand the statement "make them sql tables". I taking
about a regular ms-access mdb here.


I had assumed (perhaps wrongly) that you have some code that you are
running, and you been using set warnings to remove the prompts. As
mentioned, if you use docmd.runSql, you will get warning prompts,but if you
use currentdb.Execute, you do not get warning prompts.

I would not really want to remove those warming prompts during regular use
of ms-access, or say when you hit to delete a table, you MOST certainly want
to leave those prompts in tact, as it would far too dangerous to delete and
damage things.

The whole issue of my suggesting really centers around the "context" of what
code, and how you running those append queries now. I just assumed your
running some update code, and you wanted to elinimonate some warning prompts
(else, how did you get to the point where you turned them off??).
 
Yes, I agree. I rarely make a table for a report. It usually has to do with
multiple queries appending to a table so I can then report on that... but I
should look at these closer to see if a query would give me the same
results.

Kelvin
 
Yes, I agree. I rarely make a table for a report. It usually has to do with
multiple queries appending to a table so I can then report on that... but I
should look at these closer to see if a query would give me the same
results.
Click to expand...

Look at UNION queries if you need to string together several recordsets. They
sometimes suffer from performance issues - but typically not as badly as a
MakeTable query.

John W. Vinson [MVP]
 
I'll take a look...

Thanks


John W. Vinson said:
Look at UNION queries if you need to string together several recordsets.
They
sometimes suffer from performance issues - but typically not as badly as a
MakeTable query.

John W. Vinson [MVP]
Click to expand...
 
MDB has nothing to do with SQL


Codd would have cried if he saw you cry babies using this piece of crap
database
 
SQL Server is _NEVER_ overkill

if your developer says that it is 'too hard' then get a new darn developer!
 
note that Tony is neither MOST, VALUABLE -OR- A PROFESSIONAL

he is a MDB cry baby



'oh, but it's too hard to use sql server'

rofl

your crack addict loser MDB development is obsolete, kid
 
Kelvin Beaton said:
I realize now that I see you options, that I am usually deleting or
overwriting local tables. Ones that I setup temporarly for reports and
such... I'm guessing your options are really only for SQL tables, correct?
Click to expand...

See the TempTables.MDB page at my website which illustrates how to use
a temporary MDB in your app.
http://www.granite.ab.ca/access/temptables.htm

This will help with bloating of the FE.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
TempTables MDB?

what a stupid concept

we don't need 9-tier Access Database Spaghetti Code

you guys just need Access Data Projects




what is it about 10 times simpler?
PLUG AND PLAY!?!

MDB is depecrated
 
Su s i e D B A said:
TempTables MDB?

what a stupid concept

we don't need 9-tier Access Database Spaghetti Code

you guys just need Access Data Projects




what is it about 10 times simpler?
PLUG AND PLAY!?!

MDB is depecrated
Click to expand...

All of the above is wong.

Note that this person is really A a r o n K e m p f and that he is not an employee
of Microsoft.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Tony;

when should someone use SetWarnings OFF?

I don't like it, not one bit.

Access is 'too flaky' to turn setwarnings off; you have no idea what's
going on
 
Back
Top