C
Chris I
Access, part of Office 2003. The latest critical updates
have been obtained.
Windows XP Home SP1
peer to peer LAN
All PCs run Win XP Home SP1. The latest critical updates
have been obtained.
I was working in the db. Out of the blue, an error screen
appeared, informing me that an error in the db had
occurred, and Access would perform a repair.
I can open the db from the computer on which the db is
located, but if I try to access the db from any of the
other PCs, the following error message appears.
"the microsoft jet database engine cannot open this file
\\myname\shared active databases 4 \database name .mdb
already open exclusively by another user, or you need
permission to view its data "
This message appears even if only the PC on which the db
is stored and one remote PC are turned on. The message
appears even if the db has not been opened on the computer
on which the db is stored. [ Yes, the PC on which the db
is stored is turned on. ]
I have searched the Microsoft KB, google & yahoo.
Clean boot troubleshooting does not point to a culprit.
Thanks for your attention to my plight.
Chris I.
have been obtained.
Windows XP Home SP1
peer to peer LAN
All PCs run Win XP Home SP1. The latest critical updates
have been obtained.
I was working in the db. Out of the blue, an error screen
appeared, informing me that an error in the db had
occurred, and Access would perform a repair.
I can open the db from the computer on which the db is
located, but if I try to access the db from any of the
other PCs, the following error message appears.
"the microsoft jet database engine cannot open this file
\\myname\shared active databases 4 \database name .mdb
already open exclusively by another user, or you need
permission to view its data "
This message appears even if only the PC on which the db
is stored and one remote PC are turned on. The message
appears even if the db has not been opened on the computer
on which the db is stored. [ Yes, the PC on which the db
is stored is turned on. ]
I have searched the Microsoft KB, google & yahoo.
Clean boot troubleshooting does not point to a culprit.
Thanks for your attention to my plight.
Chris I.