Hi,
I'm having problems with Access 2000 on an XP Pro computer. The MSACCESS.EXE process hangs-up, when I exit Access.
(I’ve looked everywhere for an answer. The standard answer is that some recordset in my VB code is not closed or the ‘Set RecSet = Nothing’ is missing. This is not the problem in my case. I tried removing all the VB code, and references, and the problem still occurs.)
fyi…
I use three FREE programs to locate and diagnose computer problems. (and to see what my computer is REALLY doing).
SystemInternals has much, much more, but these three do the job.
When I exit Access 2000 (via ‘Application.Exit’or the main “X” button), the MSACCESS.EXE process keeps running (i.e. stays in memory).
The Access window closes, the taskbar button closes, the 'MyDB.ldb' file closes, the SYSTEM.ldb file locks and the MSACCESS.EXE process keeps running.
The 'File Monitor' program I use shows me that the MSACCESS.EXE process keeps reading the Workgroup info in the "C:\Program Files\Common Files\System\SYSTEM.MDW" file every 5 seconds.
If I try to re-open the Database (without killing the MSACCESS.EXE process) the 'MyDB.ldb' file gets re-created (and locks) but the Access Window wont come up.
I have to kill the MSACCESS.EXE process before I can reopen the Database, delete the locked 'MyDB.ldb' file, or delete the 'SYSTEM.ldb' file.
I'm not very informed, when is comes to Workgroups. The “.MDW” file (I found out) is the Access Workgroup information file, but I don't have any workgroups set-up. I believe this is the default file that access creates.
Could it be a corrupted default “.MDW” file?
As a test, I created a new TestDatabase that only has one table, with two values, which uses the default “SYSTEM.MDW” file.
When I open the TestDB the first time, then open a table (in datasheet view), then exit, the MSACCESS.EXE process keeps running but the Access window closes and the “.ldb” file goes away. When I re-launch the TestDB the “.ldb” file comes back and locks, (using the MSACCESS.EXE process that is still running) but the Access window will not come up.
If I open the TestDB, but open the table in design view, then exit the database, the process ends normally.
If I open the database and open the table in design view, then switch to the table view, the process ends fine when I exit.
It has something to do with opening a form, table, or query (without opening it in design view first) but the reports don't cause any problems.
fyi…
Some of the DB’s I was testing used the currently running (locked) process (of another DB) but wouldn’t open, even though an “.ldb” file was created. Other DB’s just created another MSACCESS.EXE process, then opened normally (the first time) then locked that process.
As a second test I used the Workgroup Wizard to create a new workgroup for a new Database (thinking the default SYSTEM.MDW file was corrupted) but even with a different (NEW) workgroup the MSACCESS.EXE process still freezes, and reads the new workgroup file every 5 seconds.
BUT…when I try to re-open this DB…IT OPENS! It always uses a brand new MSACCESS.EXE process, and the “DB.ldb” file does not lock when I close it again.
The good part is that I can open and close it as many time as I want, but a new MSACCESS.EXE process is created each time. The ‘SYSTEMnew.MDW’ file stays locked (via it’s “.ldb” file) the whole time.
I tested this on another computer but there weren’t any problems. Another reason why I believe it’s the default “.MDW” file located on my computer.
Why would MSACCESS.EXE keep reading the “.MDW” workgroup file, after Access is closed?
Why does it not release this file?
Am I being specific enough, or too specific? ;-)
I hope this helps.
Please let me know,
(fyi I may not respond till Monday.)
Thank you,
-Varg
I'm having problems with Access 2000 on an XP Pro computer. The MSACCESS.EXE process hangs-up, when I exit Access.
(I’ve looked everywhere for an answer. The standard answer is that some recordset in my VB code is not closed or the ‘Set RecSet = Nothing’ is missing. This is not the problem in my case. I tried removing all the VB code, and references, and the problem still occurs.)
fyi…
I use three FREE programs to locate and diagnose computer problems. (and to see what my computer is REALLY doing).
SystemInternals has much, much more, but these three do the job.
When I exit Access 2000 (via ‘Application.Exit’or the main “X” button), the MSACCESS.EXE process keeps running (i.e. stays in memory).
The Access window closes, the taskbar button closes, the 'MyDB.ldb' file closes, the SYSTEM.ldb file locks and the MSACCESS.EXE process keeps running.
The 'File Monitor' program I use shows me that the MSACCESS.EXE process keeps reading the Workgroup info in the "C:\Program Files\Common Files\System\SYSTEM.MDW" file every 5 seconds.
If I try to re-open the Database (without killing the MSACCESS.EXE process) the 'MyDB.ldb' file gets re-created (and locks) but the Access Window wont come up.
I have to kill the MSACCESS.EXE process before I can reopen the Database, delete the locked 'MyDB.ldb' file, or delete the 'SYSTEM.ldb' file.
I'm not very informed, when is comes to Workgroups. The “.MDW” file (I found out) is the Access Workgroup information file, but I don't have any workgroups set-up. I believe this is the default file that access creates.
Could it be a corrupted default “.MDW” file?
As a test, I created a new TestDatabase that only has one table, with two values, which uses the default “SYSTEM.MDW” file.
When I open the TestDB the first time, then open a table (in datasheet view), then exit, the MSACCESS.EXE process keeps running but the Access window closes and the “.ldb” file goes away. When I re-launch the TestDB the “.ldb” file comes back and locks, (using the MSACCESS.EXE process that is still running) but the Access window will not come up.
If I open the TestDB, but open the table in design view, then exit the database, the process ends normally.
If I open the database and open the table in design view, then switch to the table view, the process ends fine when I exit.
It has something to do with opening a form, table, or query (without opening it in design view first) but the reports don't cause any problems.
fyi…
Some of the DB’s I was testing used the currently running (locked) process (of another DB) but wouldn’t open, even though an “.ldb” file was created. Other DB’s just created another MSACCESS.EXE process, then opened normally (the first time) then locked that process.
As a second test I used the Workgroup Wizard to create a new workgroup for a new Database (thinking the default SYSTEM.MDW file was corrupted) but even with a different (NEW) workgroup the MSACCESS.EXE process still freezes, and reads the new workgroup file every 5 seconds.
BUT…when I try to re-open this DB…IT OPENS! It always uses a brand new MSACCESS.EXE process, and the “DB.ldb” file does not lock when I close it again.
The good part is that I can open and close it as many time as I want, but a new MSACCESS.EXE process is created each time. The ‘SYSTEMnew.MDW’ file stays locked (via it’s “.ldb” file) the whole time.
I tested this on another computer but there weren’t any problems. Another reason why I believe it’s the default “.MDW” file located on my computer.
Why would MSACCESS.EXE keep reading the “.MDW” workgroup file, after Access is closed?
Why does it not release this file?
Am I being specific enough, or too specific? ;-)
I hope this helps.
Please let me know,
(fyi I may not respond till Monday.)
Thank you,
-Varg
