Split Database / Couldn't Update Error

[Guest]

Apparently, I have missed something in splitting my database. Database setup
is as follows:

User-Level Security has been implemented. Users are not given the right to
exclusively open the database. They do have the permissions Read, Update,
and Insert Data. Permissions are assigned to Groups, and different employees
are added to different groups based on the team the employees are on.

Database is split into a Front-End and Back-End. The Back-End is saved on a
shared drive on our network, as is the Front-End. Each user has a shortcut
to the Front-End on their desktop. I have not saved a copy of the Front-End
on each user's computer which is what the Microsoft webdsite instructions
said to do. If I do that, I am not sure how to update a form in the
Front-End if I have 30 users with their own copy of the Front-End database -
I do not have network admin rights. Is it really necessary to have a copy of
the Front-End on each users computer?

The forms being used are setup for Data Entry Only. However, users are
experiencing the following error after they add data to the first field of
the form they are using:

Couldn't update; currently locked by user <name> on machine <name>. (Error
3260)

The Record-Locking for both the form and the database is setup as No Locks.
The database is shared. Why are they getting this error if the form is
opening up to a blank record?

Any help will be greatly appreciated.

Tiffany

 

[Guest]

With 30 users it would be insane to leave the front end on a shared drive.
Having the front end on the shared drive is asking for database corruption,
it is certainly doubling network traffic, and may be the cause of the problem
you are seeing.

Distribution can be a hassle, but one way to do that is to have a specific
directory where you place the newest version. Then notify users they need to
copy the new version to their own computer.

If you can't trust them to do that, then you will have to write some code
that will do it for them. One approach is to have a record in a table in the
back end that has the identifier for the current version. When the front end
starts up, check the version against a constant saved in the front end. If
they are not equal, give the user a message telling them to get the new
version, then quit the application.