Do you want to save changes to design of form 'frmXYZ'

  • Thread starter Thread starter Christopher Glaeser
  • Start date Start date
C

Christopher Glaeser

Sometimes I like to review the code for a form event, or perhaps copy the
code from a form event. To do so, I open the form in design mode, open the
property window for a command button, and open the code view for that
button. I make NO changes or edits to anything. Then I start closing
windows. When I try to close the form design, a dialog message is generated
asking, "Do you want to save changes to design of form ...". Why is this
dialog message generated when no changes have been made? If I open and
close the views within a few minutes, I know I have not made any edits and
click No. But if I work on something else for a while and come back,
sometimes I can't remember making any edits and it is very confusing. Is
this a known defect? Is there a better way to open these views so that
Access won't confuse code inspections with edits?

Best,
Christopher
 
Hi Christopher

I have not seen this documented anywhere, but regularly experience the same
annoying behavior. It's inconsistent, and happens only in A2000 AFAICT. I am
therefore guessing that it is related to the way that VB is now cobbled
together with Access, no longer part of Access as it was in A97 and earlier.
It may also indicate that the code has been decompiled, though I never
really followed that idea through.

A similar problem can occur if you have a SQL statement as the RecordSource,
and use the Build button to view it in the query design window. Access seems
to then be unable to distinguish whether the property was actually changed.

At most, these are minor annoyances compared to some of the glaring flaws in
Access, such as failure to sort properly:
http://allenbrowne.com/bug-08.html
 
I have not seen this documented anywhere, but regularly experience the
same annoying behavior. It's inconsistent, and happens only in A2000
AFAICT.
Click to expand...

I am using Access 2003, and the problem persists.

Best,
Christopher
 
Sorry: should have been A2000 and later, i.e. A2002 and A2003 as well - ever
since they cobbled standard VB onto Access.
 
Back
Top