Multiple users of Acess2000 database?

[Johan Myrberger]

Hi,

what options are available to make an Access2000 database available for
multiple users? Ultimately I's like to assign different rights (read,
update etc) for various users, per table in the database. However I'd be
happy for means of providing full access to all users, but avoiding
conflicts when updates are made.

Solutions using Access2000 by ev. share the file on the LAN, migrating
the database to another tool or using some kind of web based interface
are potentially of interest.

Any pointers to information on this topic?

Best regards
/Johan Myrberger

 

[Joseph Meehan]

Hi,

what options are available to make an Access2000 database available
for multiple users? Ultimately I's like to assign different rights
(read, update etc) for various users, per table in the database.
However I'd be happy for means of providing full access to all users,
but avoiding conflicts when updates are made.

Solutions using Access2000 by ev. share the file on the LAN, migrating
the database to another tool or using some kind of web based interface
are potentially of interest.

Any pointers to information on this topic?

Best regards
/Johan Myrberger

Microsoft Access is designed as a multi-user product. You need to look
at two features

The Big Split:
First you will want to research split databases. Here you design a back
end or storehouse where the data that needs to be shared resides. That is
all you put there. Next you build the front ends, or user databases. Here
is where all the forms, reports and queries live. You also will want to
have static data here. Things like address and phone number for district
offices, as long as they don't change often. Every user has their own front
end on their own PC. They may or may not be all the same, but they are all
using the same back end. Access comes with a sample and the help files and
the split wizard can help you work on this part.

Access works best if it does not need to move a lot of information over
the LAN which means static data is best kept on the front end databases.
Also kept on the front end machines will be most forms, reports queries etc.
This will allow the whole system to work faster and in some cases allow for
customization of some forms reports etc.


Top Secret:
I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can lock
everyone including God out.

Practice on some copies to make sure you know what you are doing.

 

[Fred Boer]

Dear Johan:

Good news! Access is multi-user right out of the box!

Please be sure to split your database; don't make the mistake of letting
multiple users access a single MDB file. Splitting the database creates a
"back-end" MDB containing only the data tables, and "front-end" MDB(s) with
the queries, forms, and reports. Look up on it in Access help and/or here:

http://www.granite.ab.ca/access/splitapp/index.htm

Assigning different rights and permissions can be done by applying Access
security.

HTH
Fred Boer

 

[Lynn Trapp]

versatile protection and control. However a simple mistake can lock

everyone including God out.

Actually, God doesn't get locked out, as long as He has the right .mdw
file....