Error message on closing database in Access2007

[Allan]

I have the same problem occuring in two separate databases, one developed in Acc2007 and an Acc2003 database opened using Acc2007.

When closing either program to exit Access, I get a message "Microsoft Office Access has stopped working. Windows is checking for a solution to the problem". It will show a status bar(?) for a few seconds then I am advised that MS Access will reopen (with both messages you have the choice of "Cancel"). Access starts again but not in the program I have just exited. On the odd occasion I have also had the choice to send an error report to Microsoft.

This does not occur on all occasions and it appears to occur after opening a particular form, closing the form with a command button and likewise to exit Access.

Both databases work fine and the only time I have the message appear is when I close the program.

I would not know where to start to try and identify the problem through a process of elimination, the only constant is that both programs have some element of Acc 2003 in them. The 2007 database has some 2003 forms converted in a temporary database to 2007 and then imported.

I would appreciate any advice please.

 

[georgedwilkinson]

You might want to check that form's On Close event. Put a break point on it if it exists. Also, check any event that fires when that form is closed (Lost Focus, Deactivate, Before & After Update, Unload, etc.).

 

[Allan]

Tks for the reply George. There is no code for 'on close' on any of the forms except the Access generated Docmd.quit button on the main form.

However I have now narrowed it down in the 2007 program to a sub-form. The subform is included on two forms I can bring up from the switchboard. On closing the database after accessing either of these forms (which contain the subform) the error occurs. In a copy of the database, I deleted the subform and the error message does not occur.

In the 2003 database, the error is as described in the original post. In the 2007 database I get the Report to Microsoft message.

The subform was converted from 2003 to 2007 and then imported to the 2007 database. It looks like I may have to rebuild it using 2007.

I also checked the Events you mentioned and there is nothing in either the subform or form that would cause any problem that I can see (although I acknowledge my limited amateur experience).

 

[ajetrumpet]

Allan,

I have had this problem on numerous occasions with forms of all types. I don't know what causes it, but I believe the forms get "stuck" in some sort of mode. Either that, or maybe there is some open memory that is causing a temporary corrupt form.

In any case, what I try to do (and this usually solves the problem) is two things:

1) Import the form into a new database
2) Edit the form in some way (add a text box or something) and then save it after every manipulation (e.g. - putting the box on the form, deleting the label, adding a control source, etc, etc...)


This has always worked for me. I remember once a while back, I was trying to change a combo box to a text box via right click, and everytime I did that, it seemsed as though Access would "tell itself", "OK, freeze up now when he saves". Because...from that point on, when I pushed the save button, the errors would start popping up. Didn't matter what I did after that, it was THAT specific event that caused the lock up. Who knows...