Sharing Database

[MissBart]

Currently I have a database that only a few people can access. I would like
to make available one report that has selection criteria available to other
users. There's nothing that any other user would need to update/edit. They
would just need to be able to select a name from the dialog box (popup form)
and print labels (report) for that person. What is the best way to do this?

 

[Larry Linson]

Currently I have a database that only a few people can access. I would
like
to make available one report that has selection criteria available to
other
users. There's nothing that any other user would need to update/edit. They
would just need to be able to select a name from the dialog box (popup
form)
and print labels (report) for that person. What is the best way to do
this?

You should have your backend (tables, relationships, and data) separate from
each user's front-end. Just for simplicity, I'd then create a separate
frontend for the "report only" users... with a form so they can choose the
user and initiate the report. I'd link the pertinent table(s) from that
front end, but not give those users edit, add, or delete capability. If you
want to complicate your life a little, you can use Access' security to limit
what they can see/do (if you are using Access 2007, you'll have to use an
MDB database if you want to use security; and you should be aware that it is
relatively easy to crack).

There's good discussion of security at MVP Tony Toews' site
http://www.granite.ab.ca/accsmstr.htm and at several other MVP sites listed
at http://sp.ntpcug.org/accesssig/default.aspx . There's also a White Paper
on Security that you can download from Microsoft. But, I'd suggest a
separate database for the ones who only need to print labels.

Larry Linson
Microsoft Office Access MVP