We are using an Access 2003 front-end/back-end program that was created by a vendor. The database uses a WG file for security. I was recently asked to provide some additional functionality to the program. I didn't want to mess with the vendor's front-end, so I created my own. I created the db, joined it to the existing WG, and everything tested fine while I was logged in as admin. However, when logging in as a regular user and opening the main form or any queries I get the following error: "You do not have the necessary permissons to use the backend.mdb object." OK, so I checked the WG permissions on the back-end and saw that the admin user had "Open/Run" permission for the database, while regular users did not. So I gave the Open/Run database permission to a regular user, logged in as the user and everything worked fine. My question is, if regular users did not need the open/run database permission to use the vendor's front-end, why do they need it for the front-end that I created? I did some research and came across the "Run Permissions" property for queries. Thinking this might be the solution, I went into all my queries and changed Run Permissions from User's to Owner's. This did not help though. Can anyone shed some light on this? Is there a way to assign permissions to a form or query rather than to a user?