Orion said:
A user is complaining that since the Upgrade of our server from
Windows 2000 Server to Windows Server 2003 he cannot access his MS
Access Database file if someone else is using it at the same time.
Where can one set a database to be used by a single user only or by
various users at once?
When a database is opened, the user opening it may have their individual
program set to open the file "exclusively" thereby blocking out all other
users. This can become the default setting and it is possible that someone
may have their copy of access set this way.
There are a number of other possibilities as well however. The one that
comes to mind here is the fact that access requires that the user have full
read right create delete modify rights to the director and file they are
opening. When they open an access file a new file is create called
samename.ldb. That is a locking database file. Sometimes these files don't
get deleted or get corrupted and they create problems.
Many times problems develop when multiple users are access the same file
on the server directly rather than using a split database. In a split
database the original database is split into two parts. The "back end"
warehouses the actual dynamic - shared data on the server and the "front
ends" are located on each user's PC and hold all the forms reports queries
and maybe some static data tables and link to the tables on the server.
This creates a lot less LAN traffic and less problems.
I hope some of that will help.
