When you distribute Access projects to users, the only security you can apply on the client side is compiling the project to an encoded .ade file. Like .mde files, projects stored in .ade format prevent users from making design changes to the front end and gaining access to your VBA source code. When you use the default integrated Windows authentication for the back-end SQL Server database, which is the recommended configuration for SQL Server, you can't apply password protection to the project. Windows authentication prevents users who haven't been assigned server logins and database permissions from opening the project's connection to the server.
To learn how to use OSQL to add logins and database permissions to MSDE, see "Adding User Logins with the OSQL Utility," p. 776. Note The Database window's Design and New shortcuts for tables and queries are enabled for all .mde users. Users need SQL Server permissions to create or alter tables, views, functions, and stored procedures. Like .mde files, macros aren't protected from design changes in .ade files. To create an .ade version of your .adp file, follow the same procedure as described in Chapter 19 for creating a .mde from a .mda file:
Note Database Creations, Inc. offers an Access Project Security Manager (APSM) add-in to enable user-level security for ADP application objects forms, reports, and controls on forms. APSM has features similar to the User-Level Security Wizard for Jet-based front-ends. For more information on APSM, which requires enabling SQL Server security for server logins and database permissions, go to http://www.databasecreations.com/. |