Microsoft Office Access has encountered a problem and needs to close

[Vic Spainhower]

I have an Access 2003 database that fails with "Microsoft Office Access has
encountered a problem and needs to close. We are sorry for the
inconvenience." when a certain form is attempted to be displayed. This form
is part of another form containing a tab control.

This has become difficult to track down because if I insert a break point at
the beginning of the "Enter" event so as to walk thru the code it doesn't
fail. I can also put a MsgBox at the beginning of the Enter event and it
won't fail.

Any ideas on how to track down the root of the problem? I have decompiled
the database and also created a new database and imported all of the objects
into the new one but nothing helped.


Vic

 

[Dirk Goldgar]

I have an Access 2003 database that fails with "Microsoft Office
Access has encountered a problem and needs to close. We are sorry
for the inconvenience." when a certain form is attempted to be
displayed. This form is part of another form containing a tab control.

This has become difficult to track down because if I insert a break
point at the beginning of the "Enter" event so as to walk thru the
code it doesn't fail. I can also put a MsgBox at the beginning of the
Enter event and it won't fail.

Any ideas on how to track down the root of the problem? I have
decompiled the database and also created a new database and imported
all of the objects into the new one but nothing helped.

Is there anything the least unusual about that form? You might try
saving it to text, then recreating it from the text file -- you can do
that from the immediate window similar to this:

Application.SaveAsText acForm, "MyForm", "C:\Temp\MyForm.txt"

Application.LoadFromText acForm, "MyForm1", "C:\Temp\MyForm.txt"

And then rename "MyForm" (the original form) to something else, and
rename "MyForm1" to "MyForm" (the original name, that is).

If that fails, my best advice would be to recreate the form from
scratch.

 

[Van T. Dinh]

Try the following Microsoft Knowledge Base articles:

http://support.microsoft.com/?id=289508

and

http://support.microsoft.com/?id=294301

and see if you can make sense of the error.

 

[Vic Spainhower]

Thanks to both Dirk and Van! I ended up going top a recent backup and
re-applying all of the changes which resolved the problem.