J
JD
Why does MSACCESS.EXE stay running after Access is closed?
Here is the test scenario:
1. create a new database and add a form. Open and Close access and check
taskmgr... MSACCESS.EXE stopped sucessfully.
2. open the database, modify the form by adding a textbox, or button. Open
and Close access and check taskmgr... MSACCESS.EXE is still running.
I have Office 2000 SP-3 and Win XP Tablet PC SP1 installed (all lated
Windows Update).
I have tested this on Windows 2000, Windows 98, and Windows XP Pro and
MSACCESS.EXE closed like it should. However Windows XP Tablet does not
close as it should. It appears it may have something to do with the
built-in controls for Access. Why does adding a button, or textbox cause
this? I assume Access is detecting an open reference. Does anyone know
which where (the file) that Access uses for the built-in controls? I would
like to compare it against the systems that are working.
Here is the test scenario:
1. create a new database and add a form. Open and Close access and check
taskmgr... MSACCESS.EXE stopped sucessfully.
2. open the database, modify the form by adding a textbox, or button. Open
and Close access and check taskmgr... MSACCESS.EXE is still running.
I have Office 2000 SP-3 and Win XP Tablet PC SP1 installed (all lated
Windows Update).
I have tested this on Windows 2000, Windows 98, and Windows XP Pro and
MSACCESS.EXE closed like it should. However Windows XP Tablet does not
close as it should. It appears it may have something to do with the
built-in controls for Access. Why does adding a button, or textbox cause
this? I assume Access is detecting an open reference. Does anyone know
which where (the file) that Access uses for the built-in controls? I would
like to compare it against the systems that are working.