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

MSACCESS.exe process does not stop when user exits Access

P: n/a
Using Windows XP SP-1 with all security udpates installed
MS Access version 10.2627.3501 SP-1 (all service packs to be installed over
the weekend)
MDAC 2.8
Jet 4.0 SP 8

When the database and access are closed, the MSACCESS.EXE process is left
running and will not allow another instance of Access to be opened until the
original process has been terminated.

I have determined that the cause of this is from a calculated field on a
subform set to display as continuos form. I have only found one other
mention of this in comp.databases.ms-access and there was no work around
provided. I would prefer to keep the calculated field on the subform. Is
the only way around this to code in the calculation into the forms OnCurrent
event, or is there another way that I have not thought of yet? Will one of
the service packs cure this? Is this such an isolated occurance that I am
likely to be one of two people in the world who has this problem?

Thanks for any help you can provide,

Mike
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"Mike" <no****@nospam.com> wrote in message
news:10*************@corp.supernews.com...
Using Windows XP SP-1 with all security udpates installed
MS Access version 10.2627.3501 SP-1 (all service packs to be installed over the weekend)
MDAC 2.8
Jet 4.0 SP 8

When the database and access are closed, the MSACCESS.EXE process is left
running and will not allow another instance of Access to be opened until the original process has been terminated.

I have determined that the cause of this is from a calculated field on a
subform set to display as continuos form. I have only found one other
mention of this in comp.databases.ms-access and there was no work around
provided. I would prefer to keep the calculated field on the subform. Is
the only way around this to code in the calculation into the forms OnCurrent event, or is there another way that I have not thought of yet? Will one of the service packs cure this? Is this such an isolated occurance that I am
likely to be one of two people in the world who has this problem?

Thanks for any help you can provide,

Mike


Okay, I have now found the true root cause of the issue. The calculated
field on the continus form had conditional formatting as well. Removal of
the conditional fomatting has eliminated the problem.

Does anyone know why this would cause Access to leave the process running?

Mike.
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.