Hi,
I have a weird problem with msaccess.exe not stopping when a user quits a database.
This is a shared database that all 10 users on a small network use. When this one user exits the database (properly), taskmgr still shows 1 instance of msaccess.exe still there. Everyone else's quits OK. All users use the Access 2000 runtime. This causes him a problem because he can't then start the database from his shortcut again (until he has End Task on msaccess.exe)
I think it's a software conflict - because it happened on this user's old PC too, and this is a brand new XP SP2 one, albeit loaded up with loads of applications. I think one of these apps is conflicting, and and wondering if anyone has seen this before which might help me narrow the search...
thanks
Rob
I have a weird problem with msaccess.exe not stopping when a user quits a database.
This is a shared database that all 10 users on a small network use. When this one user exits the database (properly), taskmgr still shows 1 instance of msaccess.exe still there. Everyone else's quits OK. All users use the Access 2000 runtime. This causes him a problem because he can't then start the database from his shortcut again (until he has End Task on msaccess.exe)
I think it's a software conflict - because it happened on this user's old PC too, and this is a brand new XP SP2 one, albeit loaded up with loads of applications. I think one of these apps is conflicting, and and wondering if anyone has seen this before which might help me narrow the search...
thanks
Rob