Securing a Report?

[MarcieFess]

I have several reports that I've spent a LOT of time on (and some of you have, too). I do not want any of the users to be able to make any changes to these reports whatsoever.

The database is split, and the reports reside in the front end. Should they be moved to the back end (is that even possible?)

What's the best way to prevent users from being able to make substantive changes to the reports? The only thing I want them to be able to do is to choose the company and store they are printing the report for...I do not want them to be able to change any of the coding in the report, nor do I want them to be able to change the format of the report.

Should I hide the reports from them? Or is there a way to prevent them from opening the report in Layout or Design view, that would possibly open a dialog box that will allow them to make a copy of the report that they can manipulate any way they desire?

 

[llkhoutx]

You could set up Access security for the report prohibiting users to view it in the design view. Someone has to be able to view it. Access password word crackers are widely available ion the Internet.

Alternatively hide the report in your database, if you're confident your users can't unhide it. Most can't.

Create a separate database with compiled objects and execute the report there.

 

[MarcieFess]

I'll definitely do that, thanks. This has taken TOO long to let them mess it up. It solves the other issue of how to make sure they can't get to other parts that I don't want them in, too.