Thanks a million Mr. Ruralguy. I will keep at this "nagging loose end"
until I find out what is the source of this problem. I will try to monitor
with the Unload event.


"ruralguy via AccessMonster.com" wrote:

All I can suggest is putting some diagnostic coede in the Unload event that
writes the current value of the properties to a text file along with a time
stamp and any other information you might fine useful. It may help you pin it
down. I guarantee you what you are describing is not normal operation and may
point to other issues with the system even though as you say it has been
running for 5 years. OS's are being patched and changed as are applications
such as Access. I would treat it like a nagging loose end.

Fred wrote:
For this particular form, I just close the form by "DoCmd.Close" only. This
is done with the "close" command button. Two other ways of closing the form
is; by "clicking" on the X (close window) and/or by any abnormal exit
(power down, task manager...etc).

I was not aware that the DoCmd.Close acForm, Me.Name, acSaveNo can change
the form property. If it does, why does this (property change) not occur
constantly. It occurs very intermittently (once in a blue moon), and to
think this
application is used by an average of 3 users a day. I've given up trying to
figure this one out. This application has been successfully running for more
than 5 years now. This is the only problem that I"ve been encountering these
past 2 years (when it started).

I appreciate your patience and help. Let me know what to do...please

===

I miss typed the string. It should have been acSaveYes instead of acYes. The
point I was trying to make is there are ways for the properties to be changed
[quoted text clipped - 7 lines]
Thanks,
Fred

--
RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/201002/1

.