After running into this problem on the db that I had written for my
client I tested a few things and have got this far:

OS Windows 7 -patched
MS Access 2003 - patched

I created a blank database and created two tables with a one-to-many
relationship. I built a form with a sub form based on the two tables
and typed in some data. This is a self contained mdb (i.e. not split)
and there is no code in the forms.

Any time I open the database and close it again, the msaccess.exe
process does not terminate - I have to manually end it using task
manager! If I remove the sub form form the main form, msaccess.exe
will terminate as expected. So it seems that the presence of a sub
form is the cause, but I don't know why.

I have placed the database in Program files and My documents to see if
it was a UAC or permissions issue but it doesn't make any difference.

Any ideas?

Paul H wrote:

I have the same issue with only one database out of the many I've developed.. Some background...the mdb was originally developed in 2003, then upgraded to 2007, then finally to 2010, using Windows XP. Then I upgraded to Windows 7, the user did not. I have the accdb set to automatically compact on close. This hangs up for me, not for the user. I can't even get to my task manager, I have to power off/on. If I take the the auto compact, then itcloses just fine for me.

I'm running 32-bit Access 2010 with 64-bit windows 7.

Also, I've had issues with Office SP1 and legacy databases crashing. Afteruninstalling SP1, I don't have any more problems with crashing databases.

This SP1 issue is very well documented online. As of 3 weeks ago, Microsoft was still trying to fix the problem. See http://answers.microsoft.com/en-us/o...1-f55d40af271b

I should have said "I have a similar issue...". It's not exactly the same issue as what you're having. But maybe if someone has an answer for you, it would fix both problems.

If you have Office SP1 installed, you might uninstall it and see if that corrects your problem. It didn't work for me but I don't have legacy database crashing anymore.

emanning <emanning (AT) kumc (DOT) edu> wrote in
news:28741533.2812.1316528984293.JavaMail.geo-discussion-forums@yqav1
3:

Turn that off. It is a useless function, and downright dangerous --
it could corrupt your database irretrievably.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

emanning <emanning (AT) kumc (DOT) edu> wrote in
news:28741533.2812.1316528984293.JavaMail.geo-discussion-forums@yqav1
3:

....adding, once you turn this off, try compacting manually, and then
see if it hangs when closing. Or if the compact reveals corruption.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On Sep 19, 5:59*pm, "Bob Barrows" <reb01... (AT) NOyahooSPAM (DOT) com> wrote:
No, it is 32 bit.

Thanks for the advice. I did a manual compact with no problem. So it must be the auto-compact that is flaky, but just on my pc with Windows 7. It works fine on the user's pc with XP.

emanning <emanning (AT) kumc (DOT) edu> wrote in
news:21615121.1916.1316697750831.JavaMail.geo-discussion-forums@yqnk4
1:

No one under any circumstances should ever ever ever use the COMPACT
ON CLOSE OPTION. It's useless 99% of the time, and downright
dangerous the rest of the time. It's an option that MS never ever
should have implemented at all.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/