In Access 2002, how do I allow users to add records or edit recor.

[Guest]

Is there a way to allow users to add, delete or edit records on a shared
Access 2002 database?

 

[Rick B]

Ummmm. they should be able to by default.

Do they have permissions? Are they getting an error?

Rick B

 

[Joseph Meehan]

Is there a way to allow users to add, delete or edit records on a
shared Access 2002 database?

From the Access end, that is the default setting.

If anyone opens it up "exclusively" then that locks it.

The usual problem is the users don't have access rights to the directory
where the file is located including open, read, edit, save, delete etc.

Access rights may be restricted using Access security or passwords.

Note: record locking, the system used to prevent conflicting edits, may
also cause some issues.

When you are sharing any Access database it is always a good idea to use
a split database design to prevent many problems.

 

[Larry Daugherty]

Hi Lisa,

Answer in two parts:

1, Unless you go out of your way to design your forms otherwise, the
defaults will give you what you desire.

2. However, for many reasons, your application should be split into a
front end and a back end. Look up Split in Access Help. Then, you should
compile your front end without errors and then: 2b. convert the MDB into
an MDE. Place a copy of the MDE on each user's desktop. Keep your copy of
the MDB in a safe place because you need to make changes in it and repeat
step 2b each time you have changed the front end.

Look on Tony Toews's site (URL is in his signature) for FE Updater, a nifty
facility Tony developed and made freely available to all who will pick it up
and work their way through it.

HTH

 

[Guest]

Thanks, Larry.

It looks like I left off part of my problem, so let me know if your answer
will still apply. Here is the rest:

I'm trying to set up an Access database on a shared network where multiple
users can add, delete, and modify records at the same time. I have been
scouring my resources and have not found the answer. The examples of Access
databases that have been previously created here only allow a handful of
users to add, delete, and modify records while all other users can only view
information.

Thanks again for your help.

Lisa

 

[Joseph Meehan]

Thanks, Larry.

It looks like I left off part of my problem, so let me know if your
answer will still apply. Here is the rest:

I'm trying to set up an Access database on a shared network where
multiple users can add, delete, and modify records at the same time.
I have been scouring my resources and have not found the answer. The
examples of Access databases that have been previously created here
only allow a handful of users to add, delete, and modify records
while all other users can only view information.

Thanks again for your help.

Lisa

That sounds like one of three things.

User level security. That will allow control of what each user can do.

Password security. That allows two levels of access depending on the
password.

Lack of full access to the directory where the file is kept. This is a
LAN issue. Each user should have full access including read edit, create
and delete.

The only thing I know of other than above (and I sure don't know it all)
would be problems with the application. This is not uncommon when a single
file is used by a number of users. When more than one user is to have
access to the data, the file should ALWAYS be split so the back end which is
shard on the server has all the data files and the front ends, which are on
each user's machine has all the queries, reports forms etc.

 

[Larry Daugherty]

Hi Lisa,

The answers before still apply.

If the ability to add and delete records varies by user then I suggest that
you review with IT to see that all of the users have the appropriate rights
in the affected folders In their Access Control List. Also, is security
applied to the databases in question? If so, see what user permissions are
in effect.

There is yet another possibility and by not knowing your whole
configuration, I'm left guessing. If every user has an MDB front end on
their system then they can get in and fiddle with the properties of the
objects in your database. If some users can add and delete records from
some forms but not while using others, it's a clue. compare the form's
properties between the systems that can and the systems that can't/

HTH