Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Access to Reports for end users
- Thread starter timlowe
- Start date
You could do it by setting up groups through Access security or you could split the database having a backend to hold your tables. Then create separate front end mdes one for Full access (containg all forms, reports, etc) the other for Reporting access only (containing only reports, maybe a GUI that lists the reports available to run).
Hope this helps.
Hope this helps.
Access security is an option, and a good one, but if you don't want the extra administration issues and such, and if all you really want is something simple but secure enough to keep regular users out of the development environment while assigning each user specific reports, then you can do the following:
Tighten up your application using custom menu bars, hiding the db container on open, hide other objects, create generic password areas, and whatever else to keep user out of your database container. Then create a table design to manage usernames and report names...even user groups and passwords if you wanted to.
Basically, you'd have a table of users. Each user can view many reports, so you'll have a related 1-to-many "reports" table. Create a "report manager" form and apply this design into the form. The idea is to query the reports table and show only those report names which are assigned to whichever user is using the report manager. I found this design also to be useful when needing to setup multiple report printing sequences.
Regarding how you allow users to access this report manager area is optional, but you can create your own user login form and populate the report list accordingly. Remember to store the actual report object name into your reports table so that when a user selects a report name, you can open the report object programmatically.
This may not be the best answer for you. True Access security is a more secure option. But I'm just letting you know of some of the creative ways to accomplish the same effect through your own interface design.
Hope this helps,
Mike Dorthick
Tighten up your application using custom menu bars, hiding the db container on open, hide other objects, create generic password areas, and whatever else to keep user out of your database container. Then create a table design to manage usernames and report names...even user groups and passwords if you wanted to.
Basically, you'd have a table of users. Each user can view many reports, so you'll have a related 1-to-many "reports" table. Create a "report manager" form and apply this design into the form. The idea is to query the reports table and show only those report names which are assigned to whichever user is using the report manager. I found this design also to be useful when needing to setup multiple report printing sequences.
Regarding how you allow users to access this report manager area is optional, but you can create your own user login form and populate the report list accordingly. Remember to store the actual report object name into your reports table so that when a user selects a report name, you can open the report object programmatically.
This may not be the best answer for you. True Access security is a more secure option. But I'm just letting you know of some of the creative ways to accomplish the same effect through your own interface design.
Hope this helps,
Mike Dorthick
- Status
Similar threads
