Why is my Packaged Access 2007 application opening read only?

I packaged an application using Access developer extensions and Access 2007 runtime. When I open the packaged application it tells me that it is read only, and I cannot update.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It has no trusted certificate included probably. Check the Options - Trust center.
SageKey is a better option for distributing Access databases but it isn't cheap.  It handles installing the runtime if necessary and creating trusted directories for the database.

The other problem may be that the user does not have Create permission on the folder where the BE is located.  Access uses a lock file to manage concurrent users.  The first user to open the database will cause Access to create the lock file and the last person to close the app will cause Access to Delete the lock file.  If Access cannot create a lock file and one doesn't already exist, Access will open the database as read only.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
smm6809Author Commented:
How do you create trusted directories, and how does that factor into the packaging of the application?
To create a trusted directory, open any Access database.  Then find the "Options" dialog.  I don't remember how to get to it in A2007.  Choose the Trust Center option and then press the Trust Center Settings button.  The final dialog will allow you to add trusted locations.  If the location is on a network drive, be sure to check the Allow Trusted Locations on my network drive.

Instead of driving myself crazy with locations, I define one path on my C: drive and another on my network work space.  As long as you check the option to trust subfolders and you always put your databases somewhere in these locations, you are all set on your local machine.  Installing for others is a different problem.  You could go to their desks and follow the same procedure or instruct them how to do it but that requires that the user have the full version of Access installed and that doesn't always happen.  If all they have is the runtime, then there is no way via the Access interface to do this.  You will need to modify the registry.  I don't have the keys handy but they are easy enough to find if you need them.

Given the symptom though, I don't think trusted locations is the issue.  Generally when a database is not trusted, you will get a security warning and be asked if you want to trust the database.  It is more of an annoyance than a lack of functionality.  Please see my first answer for the other issue.
smm6809Author Commented:
Permissions for the folder were wrong.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.