Solved

Making a Access 2007 and Access 2010 Runtime

Posted on 2011-09-08
2
322 Views
Last Modified: 2013-11-05
I am trying to make a runtime version of my application created in Access 2007 but running under Office Prof 2010. How do I do it? Is it via the Package Solution route? I have read many articles about this but I am still very confused. I also have an application created in Access 2010 - is the procedure to create a runtime for it the same as for above?
Many thanks
0
Comment
Question by:kotzejd
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 85

Accepted Solution

by:
Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 50 total points
ID: 36501646
To make a Runtime version of your application, you simply save the file with the .accdr extension. You would then deploy that file to your end users. Alternatively, you can use the Package Wizard to bulid an installation file, which can include the Access Runtime, but that's not required, and many find it to be more trouble than it's worth.

If you don't use the Package Wizard, then if your end users do NOT have the full version of Access on their machine they will need to download and install the Access Runtime, which is free and available here:

http://www.microsoft.com/download/en/details.aspx?id=10910

Once they install that file, they'll be able to use your application in the runtime mode. If they do have the full version of Access, then you don't need to deploy the runtime - just deploy your database with the .accdr extension, and the database will run.

Note, however, that you should thoroughly test your app in the runtime mode before you deploy it. There are quite a few differences between a Runtime database and a "normal" database:

http://msdn.microsoft.com/en-us/library/bb501030%28v=office.12%29.aspx
http://office.microsoft.com/en-us/access-help/deploy-an-access-2007-application-HA010218864.aspx

Also note that if your end users have the full version of Access, then they can simply switch back to the .accdb extension and have full rights to modify your database. In most cases, you're far better off deploying your file in the .accde format, which compiles the database and removes the ability for end users to modify Forms, Report and Code (macros or modules).
0
 

Author Closing Comment

by:kotzejd
ID: 36591416
I had some additional problems but decided to put on hold
0

Featured Post

Will your db performance match your db growth?

In Percona’s white paper “Performance at Scale: Keeping Your Database on Its Toes,” we take a high-level approach to what you need to think about when planning for database scalability.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This post looks at MongoDB and MySQL, and covers high-level MongoDB strengths, weaknesses, features, and uses from the perspective of an SQL user.
Traditionally, the method to display pictures in Access forms and reports is to first download them from URLs to a folder, record the path in a table and then let the form or report pull the pictures from that folder. But why not let Windows retr…
The viewer will learn how to use the =DISCRINV command to create a discrete random variable, use this command to model a set of probabilities and outcomes in a Monte Carlo simulation, and learn how to find the standard deviation of a set of probabil…
The viewer will learn how to create a normally distributed random variable in Excel, use a normal distribution to simulate the return on an investment over a period of years, Create a Monte Carlo simulation using a normal random variable, and calcul…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question