Limiting access to reports only

  • Thread starter Thread starter Parley Kennelly
  • Start date Start date
P

Parley Kennelly

I have a database that sits on my server and I want to give the individual
users the ability to print/view reports that are in the database but I do
not want to give them the ability to access/change any data via
forms/tables/queries.

Is there a way to create an access database that just has links to the
reports in the main database? I know I can link all the tables and then
copy all of the queries and then copy all of the reports. But what if I
need to change a query or report format?

Any help or suggestions will be greatly appreciated.
Oh, I'd like to do this without messing with the permissions or passwords.

TIA
Parley
 
Oops,
I forgot to mention. The Database is written in MSAccess 2k and each
workstation has MSAccess 2k installed, as well.
-Parley
 
Hi Parley,

If you link the tables to a 'backend' database and then
have 'frontend' databases on all the other machines which
need to run the reports, with all the needed reports
and/or queries, this would work fine.

If changes are made to report formats/queries, all you
need to do is update the frontend databases on all the
machines to the new version.

That's what we do with a huge database we use.

The backend stores all the data, and the front end
provbides the User Interface.

Cheers,

Tim
 
In addition, you can build the Front End report database and then "lock it
down" by hiding the database window.
Using code it is tough for non-experts to break in to your file.

You can also convert it to an mde file which is compiled and does not allow
creation of new forms or reports.
 
I have a similar situation. I have used an .mde and hidden the database
window as suggested by Joe, plus I have disabled the extended menu and the
toolbars. My users are by no means Access experts, so it works just fine.

By the way, I have placed my front end on the server as well, so I only have
to maintain one copy of it, and this works fine as well. Eventhough I have
not implemented security, wherever I need a user-specific access or action I
just use the network login to identiufy the user (who don't even know they
are identified!).

HTH,
Nikos
 
Correct!

Only prob with having the Front end on the server is the
speed issue. Accessing largish databases across a network
can slow the entire network, and the database won't
perform speedwise...

If it is only a small database, then it should be fine.

We have a lot of confidential data that needs integrity,
so use the .mde as well, and remove all the normal menus.
 
And one more point - Tony Toews distributes a free Front End Updater program
that works well.
This means you keep 1 copy on the server, and each user gets their own copy.
They always start their copy using the FE updater program which checks the
server for a new version.
Then if you create a new version you simply put it on the server and it is
distributed to each user.
Very sweet.
http://www.granite.ab.ca/access/autofe.htm
 
Tim,

It's the back end that's big (mine holds 120K+ invoices with 420K+ lines,
and keeps growing by the day), and that's always going to be on the server..
so, whether the FE is on the server as well or local, network traffic cannot
be avoided, and speed does not change practically.

Nikos
 
Back
Top