I have 2 Access 2003 databases that are exhibiting the same problem.
These are frontend databases with tables linked from a backend DB. The
problem only manifests under Windows Vista. All is good under Windows
XP.
When opened normally the database works fine. However when I have the
database open in design view and try to close it by closing the
database window, Access crashes. Same thing when I try to do a
compact and repair, because Access has to close the database to do
this. My first attempt at a solution was to copy all objects into a
new database. The problem was still there. My second attempt was to
save all objects as text and rebuild all the objects from the text
files. The problem was still there.
Now comes the enlightening part. If I copy the database and paste it
into the same folder so that the copy is named "Copy Of
OCCActionsReg.m db", the problem goes away on the copy. If I then
remove the original from that folder and rename the copy back to the
original name, OCCActionsReg.m db, the problem returns. If I then move
OCCActionsReg.m db to a different folder, the problem goes away.
THIS IS INSANE. For some reason, if the database is called by its
original name and run from its original folder it crashes when I close
the database window in design view. If I change the file name or the
folder, all is good. This only happens under Windows Vista.
I'm now starting to think that there's nothing wrong with the database
itself, or the problem wouldn't go away just because I've renamed the
file or changed its location. I'm starting to think that Vista is
trying to drive me over the edge! Can anyone offer any clues as to
what is going on here???
These are frontend databases with tables linked from a backend DB. The
problem only manifests under Windows Vista. All is good under Windows
XP.
When opened normally the database works fine. However when I have the
database open in design view and try to close it by closing the
database window, Access crashes. Same thing when I try to do a
compact and repair, because Access has to close the database to do
this. My first attempt at a solution was to copy all objects into a
new database. The problem was still there. My second attempt was to
save all objects as text and rebuild all the objects from the text
files. The problem was still there.
Now comes the enlightening part. If I copy the database and paste it
into the same folder so that the copy is named "Copy Of
OCCActionsReg.m db", the problem goes away on the copy. If I then
remove the original from that folder and rename the copy back to the
original name, OCCActionsReg.m db, the problem returns. If I then move
OCCActionsReg.m db to a different folder, the problem goes away.
THIS IS INSANE. For some reason, if the database is called by its
original name and run from its original folder it crashes when I close
the database window in design view. If I change the file name or the
folder, all is good. This only happens under Windows Vista.
I'm now starting to think that there's nothing wrong with the database
itself, or the problem wouldn't go away just because I've renamed the
file or changed its location. I'm starting to think that Vista is
trying to drive me over the edge! Can anyone offer any clues as to
what is going on here???
Comment