Split Database / Couldn't Update Error

Tech-Archive recommends: Fix windows errors by optimizing your registry

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
.

Relevant Pages

  • RE: Split Database / Couldnt Update Error
    ... Having the front end on the shared drive is asking for database corruption, ... > shared drive on our network, as is the Front-End. ... > The forms being used are setup for Data Entry Only. ...
    (microsoft.public.access.forms)
  • Re: Dynamic listing in a form - Thanks
    ... tables in a separate database and include them in your main front-end as ... The database bloat that PCD mentioned. ... > "Alp Bekisoglu" wrote in message ... >> I do get everything I want and display it in a MsgBox. ...
    (microsoft.public.access.formscoding)
  • Re: Splitting and networking database
    ... the front-end will have "links". ... but that computer has no CD burner to burn an install package ... I have never split a database before, ... my client's network ...
    (microsoft.public.access.tablesdbdesign)
  • RE: Deny access to certain users
    ... to as the front-end) into two parts; Access provides a wizard for doing this. ... This will put your tables in the back-end, and leave your forms, queries, ... If you will eventually have multiple applications to manage, ... table, applications table, and UserApplications tables in a separate database ...
    (microsoft.public.access.forms)
  • Re: Splitting and networking database
    ... data on your company's PC and carry the front-end home to ... my client's network ... Use the wizard to split the database. ... Install the package on each of the computers which need to access the ...
    (microsoft.public.access.tablesdbdesign)