Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Have been working in an Access 2007 application for over 3 weeks and it should be ready now. Anyway, I know (and tried) that "Make ACCDE" can actually split the raw data from the application itself so you can run it using the Access RunTime.

The question is... can I deploy my app for general use and modify a separate copy of the forms/views inside the application to deploy it when it´s ready without touching the data?

share|improve this question

Yes, you can (and you should!!) split your application into two Access databases:

  1. A backend containing all the tables.
    Put this somewhere on a central network share.

  2. A frontend containing code, forms, records and so on...basically everything except the actual tables (which are in the backend).
    You can link the tables from the backend here, and each user should have his own copy of the frontend on his local machine.
    It's quite easy to deploy the frontend in a way that it auto-updates each time a user runs it.

If you split your app this way, you can just deploy it now and your users can start using it.
Later, you can modify the forms and reports (or add new ones) and just deploy a new version of the frontend to your users, without them even really noticing it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.