By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,665 Members | 2,802 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,665 IT Pros & Developers. It's quick & easy.

Closing a form causes crash

P: n/a
One form in my Access 2000 mdb causes a crash whenever I close it. The
crash is of the type where I get a "Please tell Microsoft about this
problem".

Easy, you think! Well, here are the things I've tried already, all to
no avail:

Followed Microsoft's advice and downloaded SR-1 and installed it.

Rebooted the computer.

Restored the system to a checkpoint I took a few days ago.

Imported a version of the form from an older mdb (where it works fine).

Started with a blank new database and imported everything into it.

Completely removed the OnClose event procedure.

Tried to recreate the problem with other forms in the same mdb.

Closed it using File > Close rather than the X. This appears to work
the first time, but when I open the form a second time, the first copy
reappears, and neither of the two gets repainted correctly.

Running out of ideas. Any more ideas I should try? Thanks.

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Di
Before you copied the objects to a new database, did you copy the code
separately and select "No" to the "Has Module" property and save the
form first?

Had this problem with a database converted from 97.

D...

Composer wrote:
One form in my Access 2000 mdb causes a crash whenever I close it. The crash is of the type where I get a "Please tell Microsoft about this
problem".

Easy, you think! Well, here are the things I've tried already, all to no avail:

Followed Microsoft's advice and downloaded SR-1 and installed it.

Rebooted the computer.

Restored the system to a checkpoint I took a few days ago.

Imported a version of the form from an older mdb (where it works fine).
Started with a blank new database and imported everything into it.

Completely removed the OnClose event procedure.

Tried to recreate the problem with other forms in the same mdb.

Closed it using File > Close rather than the X. This appears to work
the first time, but when I open the form a second time, the first copy reappears, and neither of the two gets repainted correctly.

Running out of ideas. Any more ideas I should try? Thanks.


Nov 13 '05 #2

P: n/a
Thanks for that, Di. After posting, I did think of eliminating all the
form's code by setting "Has Module" to No. This didn't work, but...

I delved into one of the subforms of the form. In one, a continuous
form, the VBA code instantiated a Collection object, and in its Unload
procedure it set the object to Nothing. Once I removed this (by moving
the shared Collection into the Parent), the problem stopped.

A self-inflicted wound. Sorry to have troubled you. Let all learn
from this: don't share an object among all the instances of a
continuous form. It seemed to work for a while, but suddenly it didn't
work any more.

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.