Terminal Server Causing "File Already In Use" - WHY?

[DaveH]

We have an Access application that has been used in-house for a few years without problem. Recently the application was moved to Terminal Server and ALL remote users were given ReadOnly access to the directory and file share where the Access database is located. The database itself does NOT reside on Terminal Server. Remote users are now receive "File already in use" messages whenever more then one person tries to connect to the database. Internal users are not affected. The only differences internally is that a handful of people have Change permission and the remainder have ReadOnly. The internal users connect to the database directly rather then through Terminal Server.

(1) Why is this message being received if the remote users connect to the db as ReadOnly?

(2) How can we avoid this message?

Thanks, Dave

[andi_g69]

I am not familiar with Terminal Server, however I remember something in regard to access and permissions:
Access creates a .LDB file when a connection to the database is opened. In order to be able to create that file the user connecting needs change rights.
I came across this issue when I used an Access DB within a web application. You can check MS Knowledge base for your error message, in my case they had a detailed article matching my symptoms.