Microsoft Office 2000/Visual Basic Programmer's Guide

Managing Client/Server Solution Security

An Access project file can't use the same user-level security features that an Access database file can. The data and other objects stored on your SQL Server can be fully secured by using SQL Server's security features. To secure server-side objects, use SQL Server's SQL Server Enterprise Manager, Transact-SQL statements, or the SQL Server Security dialog box in Access (Tools menu, Security submenu, Database Security command). For information about securing SQL Server databases, see SQL Server Books Online, or click the Help button in the Access SQL Server Security dialog box and the Help button in the properties dialog boxes displayed from the main dialog box.

To secure the objects stored in your Access project file, Access provides three features:

• Startup options   You can set options in the Startup dialog box (Tools menu, Startup command) to restrict access to default menus and toolbars, the Database window, and special keys. You can then set the AllowBypassKey property to False to prevent users from holding down the SHIFT key to override these options. For more information about setting startup options, see Chapter 18, "Securing Access Databases."
  
  
• Locking your VBA project   You can secure VBA code in an Access project by locking your VBA project with a password. For information about locking a VBA project, see Chapter 17, "Securing Office Documents and Visual Basic for Applications Code."
  
  
• Saving as an .ade file   To secure the design of forms, reports, and VBA code in your Access project file, you can save the file as an .ade file. Saving as an .ade removes your Access project's VBA source code and prevents users from changing the design of forms and reports. For information about removing your Access project's VBA source code, see Chapter 18, "Securing Access Databases."