Access lock file location redirection?

[Justin]

When an Access front end DB is stored on a shared network directory, is there
a way to redirect the lock files so they are created and managed on the users
workstation, rather than created and managed on the network directory where
the DB resides?

It's well documented that Novell and Access have a long history of problems,
and we have the traditional network errors with multiple users trying to use
a DB on the network, however we've discovered that when an instance the front
end DB is moved to each users workstation, rather than having a shortcut for
each user to the front end DB on the share, the DB works as designed.

The draw back to that workaround is that we would have to 'push' these
instances to each users workstation with our application management server,
thus creating an IT nightmare. The issue appears to be how the locks are
managed on the local workstation rather than on the network share.

Does anyone know if that can be done or have any other suggestions?

 

[George Nicholson]

we've discovered that when an instance the front
end DB is moved to each users workstation, rather than having a shortcut
for
each user to the front end DB on the share, the DB works as designed.

Front ends should never be shared by multiple simultaneous users. Access was
never designed to support that.
So you have discovered that Access works as intended when you use it as it
was intended. Good to hear.

The draw back to that workaround is that we would have to 'push' these
instances to each users workstation with our application management
server,
thus creating an IT nightmare.

Don't push. Pull

http://www.granite.ab.ca/access/autofe.htm
Tony Toews Front-end updater

Tony's site also provides links to alternate solutions, but the general
approach is the same across the board: Automate the Pulling of fe updates
from server to user.

 

[Justin]

Thanks for the confirmation, this is what I suggested to the project team as
well but wanted to get a second opinion.