Split Access database on shared network drive

  • Thread starter Thread starter Lei
  • Start date Start date
L

Lei

Hi,

The real situation is: one admin need to update the data
in the
table frequently, while more than 30 users need to view
each of
their individual report based on the update of the table
from the
front-end.

Here, I have an access database called "db1.mdb" with
user_level
security set up already. After I split the database into
front-end
and back-end, I got another back-end database
called "db1_be.mdb".

So, what should I do next in order to install the
databse? Do I need
to put the "db1_be.mdb" and "db1.mdb" both on the shared
drive,
together with the corresponding system.mdw or something
else?

Detailed instructions will be highly appreciated!
Lei
 
db1_be.mdb and the workgroup file belong on the network share. The
front end should be copied to each user's local drive and linked to
the BE on the network drive.

As for restricting the users to seeing their own information -- it is
not clear to me whether you have 30 different reports or you have one
report that views the same data in 30 different ways for the 30
different users. The latter method is the right way to do it.

The report should be based on a query, rather than on the raw table.
One of the criteria in the query should reference the CurrentUser()
function so that it returns only the records appropriate to the user.
Once you have designed the query, you change its Properties so that it
runs with the Owners Permission. This query is now a RWOP, or Run With
Owners Permission query. Then you deny all the users permission to
read the data from the raw table -- instead they must use the RWOP
query.

It's explained in the Microsoft Security FAQ. I have also written
detailed instructions about (IMHO) proper configuration of user level
security. You can find both at www.geocities.com/jacksonmacd


Hi,

The real situation is: one admin need to update the data
in the
table frequently, while more than 30 users need to view
each of
their individual report based on the update of the table
from the
front-end.

Here, I have an access database called "db1.mdb" with
user_level
security set up already. After I split the database into
front-end
and back-end, I got another back-end database
called "db1_be.mdb".

So, what should I do next in order to install the
databse? Do I need
to put the "db1_be.mdb" and "db1.mdb" both on the shared
drive,
together with the corresponding system.mdw or something
else?

Detailed instructions will be highly appreciated!
Lei
Click to expand...


**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
If you split the database you now have a front end and a
back end. Your front end is the one that is placed on
each users computer and the backend is placed on a shared
network drive. Your front end contains everything (i.e.
forms, queries, macros) and your backend just contains
that table which is linked to the frontend. So whenever
someone updates the frontend, it will automatically
updated the backend table. Make sure that your shortcut
to your frontend database contains the new workgroup file
that you created when you used the security wizard. Hope
this helps

Mike
Access MVP
 
Back
Top