M
Matt
I am having the same problem and I'm sure I can clarify for the original poster.
I have a split Access Database and still have this problem. For argument sake, call them FrontEnd.mdb and BackEnd.mdb.
When a user has FrontEnd.mdb open, I can't open either FrontEnd.mdb and BackEnd.mdb. This all used to work dandy until I upgraded from Win2K pro to WinXP.
Basically, if there is an LDB file open for ANY access database, I am unable to open it on my XP machine. Once that LDB file disappears (I.e. all other users exit), I can open it just fine.
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
I have a split Access Database and still have this problem. For argument sake, call them FrontEnd.mdb and BackEnd.mdb.
When a user has FrontEnd.mdb open, I can't open either FrontEnd.mdb and BackEnd.mdb. This all used to work dandy until I upgraded from Win2K pro to WinXP.
Basically, if there is an LDB file open for ANY access database, I am unable to open it on my XP machine. Once that LDB file disappears (I.e. all other users exit), I can open it just fine.
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com