This is a multi-part message in MIME format.

------_=_NextPart_001_01C217A4.696D9272
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Every now and then, Access will force users to save queries without the
option of canceling, nor does it normally warn when deleting, updating,
or appending.  A compact and repair will fix this problem, but what is
causing Access to go flaky like this?    It is usually rare, but I have
one database that the problem is epidemic.

------=_NextPart_001_0003_01C2184C.9B1E23A0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I would check to see if the SetWarnings has been set to False in code or 
macro or Tools/Options/Edit make sure to put a check in Action Queries. T
hat should get your notifications in order. Hope this helps.

Kenny
----- Original Message -----
From: Gregory Montague
Sent: Wednesday, June 19, 2002 11:20 AM
To: Access
Subject: [access] Access Forcing to User to Save Queries

Every now and then, Access will force users to save queries without the o
ption of canceling, nor does it normally warn when deleting, updating, or
 appending.  A compact and repair will fix this problem, but what is caus
ing Access to go flaky like this?    It is usually rare, but I have one d
atabase that the problem is epidemic.
 
 
--- Change your mail options at http://p2p.wrox.com/manager.asp or to uns
ubscribe send a blank email to  Get mo
re from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Are you using transactions in your code? Any chance there's a missing 
COMMIT somewhere?

I came across this problem many years ago, and I think it was caused by 
Access being in the middle of a transaction. But my memory is not what it 
once was...

Brian


Every now and then, Access will force users to save queries without the
option of canceling, nor does it normally warn when deleting, updating,
or appending.  A compact and repair will fix this problem, but what is
causing Access to go flaky like this?    It is usually rare, but I have
one database that the problem is epidemic.

Just so you know, I have seen this on occasion also. It is another of the 
quarky thing in Access 2000. I was not able to pin it down but I think it 
might just be a bug in SP-2. However, since it is sporatic, it is 
impossible to track down and if you can't reproduce it Microsoft will tell 
you it is an internal problem with your system!

Be aware that since I did a clean load of my machine and did NOT reload 
VB6 with this load I have not run into the problem. Also be aware the VB6 
seems to have some other conflicts with programing in Access 2000. Again, 
Microsoft could not reproduce the problem so they passed it off as our 
system (even though the same problem was reproduced on my home computer 
which was new and loaded at the manufacturer).

Sorry about the blowing off steam at MS but they can be frustrating at 
times.

Amy


> Are you using transactions in your code? Any chance there's a missing 
C> OMMIT somewhere?

> I came across this problem many years ago, and I think it was caused by 
A> ccess being in the middle of a transaction. But my memory is not what 
it 
o> nce was...

> Brian

> 
E> very now and then, Access will force users to save queries without the
o> ption of canceling, nor does it normally warn when deleting, updating,
o> r appending.  A compact and repair will fix this problem, but what is
c> ausing Access to go flaky like this?    It is usually rare, but I have
o> ne database that the problem is epidemic.

It's definitely older than Access 2000. My problems happened under either Access 97 or back in the stone
age of Access 2.0!

>  from:    Amy Wyatt <amyw@c...>
>  date:    Fri, 21 Jun 2002 16:40:20
>  to:      access@p...
>  subject: Re: [access] Re: Access Forcing to User to Save Queries
> 
> Just so you know, I have seen this on occasion also. It is another of the 
> quarky thing in Access 2000. I was not able to pin it down but I think it 
> might just be a bug in SP-2. However, since it is sporatic, it is 
> impossible to track down and if you can't reproduce it Microsoft will tell 
> you it is an internal problem with your system!
> 
> Be aware that since I did a clean load of my machine and did NOT reload 
> VB6 with this load I have not run into the problem. Also be aware the VB6 
> seems to have some other conflicts with programing in Access 2000. Again, 
> Microsoft could not reproduce the problem so they passed it off as our 
> system (even though the same problem was reproduced on my home computer 
> which was new and loaded at the manufacturer).
> 
> Sorry about the blowing off steam at MS but they can be frustrating at 
> times.
> 
> Amy
> 
> 
> > Are you using transactions in your code? Any chance there's a missing 
> C> OMMIT somewhere?
> 
> > I came across this problem many years ago, and I think it was caused by 
> A> ccess being in the middle of a transaction. But my memory is not what 
> it 
> o> nce was...
> 
> > Brian
> 
> > 
> E> very now and then, Access will force users to save queries without the
> o> ption of canceling, nor does it normally warn when deleting, updating,
> o> r appending.  A compact and repair will fix this problem, but what is
> c> ausing Access to go flaky like this?    It is usually rare, but I have
> o> ne database that the problem is epidemic.
> 

I think I found the source of the problem: Macros vs. Code.

The database was originally programmed (by someone else) with Macros
running everything.  Since the database does a lot of append, delete,
and update queries, many Macros being with the command to turn off
warnings.  In a Macro this works fine, it turns off the warnings for the
duration of the Macro only, but when running the command in code, a
command turning the warnings back on must be given or else it just stays
off.  So if the command to turn off exits a query, there will be no
warning "Do you want to save?"

I fixed the problem by adding a command to turn the warnings back on at
the end of functions and subroutine that turn them off.    I also added
the command in error handling in case something bombs.

That's the best I could figure out in anycase.