Because permissions are stored with application databases, and accounts and passwords are stored with workgroups, users must have access to both the appropriate databases and workgroups. To make an application database (or databases) and workgroups available to users, you can do any of the following procedures:
You might not want to give users a copy of the workgroup information file that defines the workgroup you used when you created the application, because then users might get full permissions to databases and objects (if they can guess a password and log on to Access as members of the Admins group).
Each user must have a copy of Access in order to run your application. If you want users to run an application without having a copy of Access on their computers, you must use the Package And Deployment Wizard included in the MS Office 2000 Developer's Edition. This wizard includes the files necessary to use the run-time version of Microsoft Access. It has its own setup program that you can use to create a custom run-time setup for each user’s computer.
Go to page:
If you are serious about your Microsoft Access security, then you should check out Garry Robinson's book Real World Microsoft Access Database Protection and Security
About the book:
Microsoft Access is the most popular desktop database in the world today and its very popularity means that its security measures can be easily compromised. Real World Microsoft Access Database Protection and Security takes a different approach than all the other Access books in the market by focusing from the start on all the issues that will help protect your database. It approaches protection and security from a task-by-task perspective and provides details that when put together will make your database more secure.
This book will help you to keep your staff from looking at your salary tables, stop your customers from looking at the design of your software that you distribute, and help you decide which security options are worth doing and which are generally a waste of your time.
Garry writes from a very experienced developer's point of view and he discusses in detail how to program all types of security issues including hiding tables as system tables, producing databases that password cracker software cannot easily crack, backing-up databases, menus, queries, and even user surveillance.