Processing hanging

  • Thread starter Thread starter QB
  • Start date Start date
Q

QB

I have figured out which form is making my db hang from closing the process
once the database is closed, but was hoping someone might know how I can
identify the excat culprit. Is there a way to view open variable after I
close a form, see what is still running, which should not be, so I can
finally fix this once and for all?

QB
 
Why not use debug and single-step thru the code (I'm assuming there is code
behind the form)?
What are you doing when this hanging occurs?
What version of Access?
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".
 
Here it is:

I open my db and my switchboard open. If I select/open a specific form, do
nothing, and close it and then close the db. The process, msaccess.exe,
remain in the task manager.

If I do the same with any other form, it closes properly.

Now the issue is that the form in question has numerous sub-form, so
identifying the source, is difficult. Hence the question for a good approach
to find the culprit.

It is an Access 2000 db running on runtime 2002.

As for steping through the code, it all runs fine. No errors are raised.
But how do I see if there are variables left over once a form is closed?

Thank you,

QB
 
You can't have a form open if the database is closed. Once the database is
closed (i.e. there is no LDB file), everything within it is closed.
Is that form or its subforms doing anything special?
Make a copy of your database and then...
Try deleting everything in the database except that form and see if this
still occurs.
Try deleting just that form and see if it still occurs.
Try creating a new empty database and importing all the objects to it.
Are you up to date with service packs?
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".
 
I understand I can't have a form open if the db is closed. The fact is that
the form in question, or one of its sub-forms is creating an instance.. some
code... that obviously isn't terminating properly and thus stoping the
msaccess process to not close properly.

I was hoping there was a way to see what remain 'active' once I close the
form to try and track down where it is created.

Yes, I had thought of one by one deleting the sub-forms.... but this will be
very long. I was sure there would be a better approach.

As far as pc setup. The pcs are out of my hands. They all seem to be at
different states, which I know is far from great, but I can't do a thing
about it. The only thing I control is the db.

Thank you for the advice.

QB
 
Back
Top