Doesn't ask Save/Don't Save, Delete/Don't Delete!!!

[Bonnie]

I really need some help on this one. Using A02 on XP. This
happens every few months or so and drives me nuts. I'm
just working away in a query, exploring changes, editing,
etc. Decide to close and don't save so I can start over
and guess what folks? IT DOESN'T EVEN ASK! Sorry for the
caps but it is frying my frizzle that it happens. This can
happen when I'm in a query, form, report or anything in
design view. It happens when I select Query, New and play
around with a temp job and want to close and not save the
query. As soon as I close, it goes straight to the 'what
do I want to name it dialog box'. I close everything down
and reboot and usually it straightens out but sometimes it
happens, I reboot, work okay for 15 minutes or so (I test
it) and then got back to my work and bingo, it does it
again!!!

I have asked our HelpDesk guys but they can't figure it
out. Any clue on where to look for an answer to this one?
Any help or advice would be greatly appreciated. THX!

 

[Allen Browne]

The symptoms you describe suggest that your database is corrupting.
The most likely cause is Name AutoCorrect.

For suggestions on how to avoid corruptions while you are developing your
database, see:
Preventing Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-25.html

 

[Bonnie]

Allen, you are a crankin' genius! Thanks bunches for the
site. Even found another problem addressed (#Deleted). I
checked my DB and I'll be darned but I didn't turn off
that danged autocorrect. (I usually don't create new
stuff, just take care of my existing DBs.)

Quick question: in Prev.Corr. you show top preventive
action is to "Log users in/out of the DB to see which
users/pcs are crashing out." I know how to open a DB on
my PC and login as another user (I have the password DB,
too), but how do I determine who is closing improperly by
doing that? Or do you refer to something else?

Thanks again for your help and thanks for being part of
the newsgroups. Your advice is always sound.

 

[Allen Browne]

What I mean by logging users in and out is to create a logging table. Append
a record when the database opens, and update the entry when they log out.

Use the Open event of your startup form (or AutoExec macro) to record the
login by executing an Append query statement:
dbEngine(0)(0).Execute "INSERT INTO ...
You can get the machine name from this link:
http://www.mvps.org/access/api/api0009.htm
and the Windows user name from this link:
http://www.mvps.org/access/api/api0008.htm
or use CurrentUser() if you are running Access security.

For logging out, Access has no Application Close event, so keep a hidden
form open, and use its Unload event to execute an UPDATE query statement for
the most recent record of the same user/machine with the log-out date/time.

It's then dead simple to query this log table to find which users/machines
are crashing out.

 

[Bonnie]

Allen,

Thank you first of all for watching the thread and
secondly for the great reply. I already track who creates
what and when and who edits certain things and when.
You've given me a new project! Thanks bunches!