How to Set Up a Trusted Location in Microsoft Access

What Is a Trusted Location in Microsoft Access?

A trusted location is a local folder or permitted network path that has been designated as safe in the Microsoft Office Trust Center. When an Access database is opened from that location, Access assumes the file can be trusted and enables its active content without asking the user to enable it each time.

Active content can include:

• VBA procedures and startup code
• Access macros
• ActiveX controls
• External data connections
• Automation involving Excel, Outlook, or Word
• Application programming interface calls and add-ins

Why Access Displays a Security Warning

Microsoft Access evaluates a database's location and security status when the file opens. If Access does not trust the file or its location, it may disable executable content and display a yellow Message Bar with a security warning and an Enable Content option.

Depending on the file and security policy, users may experience:

• VBA code or macros that do not run
• Startup forms or AutoExec macros that fail to execute
• Buttons that appear unresponsive
• Automation and external data connections that are disabled
• Repeated prompts to enable content

Adding an approved application folder as a trusted location prevents these interruptions, but it should be done only after the database and its source have been verified.

How to Add a Trusted Location in Microsoft Access

The Trust Center steps are substantially the same in supported desktop versions of Microsoft Access. The labels may vary slightly by release or organizational policy.

1. Open Microsoft Access.
2. Select File.
3. Select Options.
4. In the Access Options window, select Trust Center.
5. Select Trust Center Settings.
6. Select Trusted Locations.
7. Select Add new location.
8. Enter or browse to the dedicated application folder.
9. If required, select Subfolders of this location are also trusted.
10. Add a description that identifies the application or business purpose.
11. Select OK until all settings windows are closed.
12. Close and reopen the Access database from the trusted folder.

Microsoft provides current instructions for adding, changing, and removing trusted folders in its official Trusted Location documentation.

Recommended Folder for an Access Front End

In a properly split multi-user application, each user should run a separate front-end file from a local folder on that user's computer. A dedicated folder such as the following is easier to secure, support, and update than a broad folder shared by unrelated files:

C:\AccessApps\ApplicationName\

A reliable deployment normally follows this pattern:

• The front-end ACCDE or ACCDB file runs from the user's local application folder.
• The local application folder is configured as the trusted location.
• The shared Access or SQL Server backend remains in its controlled data location.
• An updater checks for and installs approved front-end releases.
• Ordinary users receive only the folder permissions required to run the application.

See Microsoft Access Front-End Deployment Best Practices and Access Deployment Automation for a complete multi-user rollout strategy.

Should You Trust a Network Location?

Access can permit network-based trusted locations, but Microsoft does not recommend enabling them broadly. Network trusted locations increase risk because every approved file in the shared folder can run active content without the normal Trust Center warnings.

If a network trusted location is genuinely required, the option appears under File → Options → Trust Center → Trust Center Settings → Trusted Locations as Allow Trusted Locations on my network (not recommended). An administrator may disable or control this option through organizational policy.

Microsoft recommends restricting network trusted locations for most users and centrally managing approved exceptions. Review Microsoft's Trusted Locations security guidance for Office.

UNC Paths Versus Mapped Drive Letters

A mapped drive and a UNC path can point to the same network folder but still be treated as different location strings. For example:

Configure the same path format that users and deployment scripts actually use. UNC paths are generally more consistent because drive-letter assignments can differ between workstations, but your IT policies and Office configuration determine what is permitted.

Using Trusted Locations in a Multi-User Access Database

A trusted location supports executable application content, but it does not replace correct multi-user architecture. For a shared Access application:

• Split the database into front-end and backend files.
• Give every user a separate local front-end copy.
• Trust only the local front-end application folder.
• Keep the shared backend in a stable Windows file-server folder or SQL Server.
• Use wired, reliable network connections where practical.
• Back up the backend independently of the local front-end files.
• Deploy front-end revisions through a controlled update process.

Continue with Microsoft Access Multi-User Best Practices, How to Split a Microsoft Access Database, and Access Backup and Recovery Best Practices.

Managing Trusted Locations Across Multiple Computers

Manually configuring each computer may be practical for a small workgroup. Larger organizations should consider centrally managing approved folders so settings remain consistent and users cannot create overly broad security exceptions.

Microsoft documents administrative options for Trusted Location policies, including approved paths, network locations, disabling all trusted locations, and controlling the mix of policy-defined and user-defined locations.

Troubleshooting a Trusted Location in Microsoft Access

If the security warning continues after adding the folder, check the following items in order.

1. Confirm the Exact File Location

Verify that the database is physically stored inside the trusted folder. A shortcut located in a trusted folder does not automatically make the shortcut's target trusted.

2. Compare the Complete Path

Confirm the configured folder matches the path Access is using, including the server name, share, mapped drive, and subfolder. If the database is in a child folder, either trust that exact child folder or intentionally enable the subfolder option.

3. Close and Reopen Access

Close the database and reopen it from the approved folder after changing Trust Center settings. If necessary, close all Access instances before testing again.

4. Check for Administrative Policy

If the Add, Modify, Remove, network, or subfolder options are unavailable, an administrator may be enforcing Trusted Location settings through Group Policy, Cloud Policy, or Microsoft Intune.

5. Check Whether the File Is Blocked

Windows can mark files downloaded from the internet or received as attachments. Review the file's Windows properties and your organization's security policies. Do not unblock a file unless its origin and contents have been verified.

6. Confirm the Warning Is Actually a Trust Center Warning

Missing references, broken VBA, unavailable linked tables, startup errors, and damaged database objects are separate problems. A trusted location enables approved active content; it does not repair application code or database corruption.

If the problem is not resolved by the Trust Center configuration, review our Microsoft Access Database Repair and Troubleshooting Guide or Access Error Handling and Debugging Guide.

Trusted Location Security Best Practices

• Trust the smallest practical folder rather than an entire drive.
• Use one controlled folder for each deployed application or approved application group.
• Allow only authorized personnel or the deployment process to add or replace application files.
• Give normal users read and execute access when they do not need to modify the application file.
• Enable trusted subfolders only when the application design requires them.
• Do not place unreviewed email attachments or downloaded databases in a trusted folder.
• Prefer a local trusted front-end folder instead of a broadly trusted network share.
• Document trusted paths as part of the application's deployment and support procedures.
• Periodically review configured locations and remove paths that are no longer required.

For a broader security review, see the Microsoft Access Security Hardening Guide.

Frequently Asked Questions

Related Microsoft Access Resources