unexpected form properties date changes

  • Thread starter Thread starter Sol
  • Start date Start date
S

Sol

After designing several forms and making sure they worked
the way I wanted them to, Access seemed to have changed 21
of the forms Properties Created and Modified dates to read
as the same date and time. However when I check this
information in the MSysObjects table, the original dates
and times are listed.

The result is the database loses the forms and does not
recognize the forms or associated modules and gives a
multiple "You canceled the previous operation" error
message, cannot save error messages, unable to find module
error messages and more...

I've tried deleting the offending forms and replacing them
but when replaced with a form of the same name with the
same functionality it produces the same results or when
replaced with a form of the same name with different
functionality it produces the same results or even when
replaced with a form of a different name but the same
functionality also produces the same result. Weird...

Has anyone come across this problem before? If so, any
advice to correct the problem or avoid it other than start
from scratch?

Thanks.
 
Sol said:
After designing several forms and making sure they worked
the way I wanted them to, Access seemed to have changed 21
of the forms Properties Created and Modified dates to read
as the same date and time. However when I check this
information in the MSysObjects table, the original dates
and times are listed.

The result is the database loses the forms and does not
recognize the forms or associated modules and gives a
multiple "You canceled the previous operation" error
message, cannot save error messages, unable to find module
error messages and more...

I've tried deleting the offending forms and replacing them
but when replaced with a form of the same name with the
same functionality it produces the same results or when
replaced with a form of the same name with different
functionality it produces the same results or even when
replaced with a form of a different name but the same
functionality also produces the same result. Weird...

Has anyone come across this problem before? If so, any
advice to correct the problem or avoid it other than start
from scratch?

Thanks.
Click to expand...

I'm not entirely sure I understand what's happening, but my first
reaction is that it's not anything I've heard of before. However, I
wonder if it could in some way be related to the operation of the Name
AutoCorrect (mis)feature. Do you have Name AutoCorrect enabled? It's
on the General tab of the Tools -> Options... dialog, and is enabled by
default in new databases. If it is enabled, disable it by un-checking
the Track name AutoCorrect info box, and then see if the problem still
occurs.
 
Back
Top