Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


converting msaccess application into a standalone application

Posted on 2011-02-18
Medium Priority
Last Modified: 2012-05-11
Hi Expert

I am thinking about creating an application for distribution. I am very familiar with MSAccess so I'd like to develop the application in access. I know about converting the application to mde but that still requires the user to have access installed on their computer.

So the question is what are the possible ways to convert an access application into a standalone application that can run on PC without msaccess licence.

At this stage I am open to suggestion the end result could be a browser based or exe application. Browser based will be better as it will provide cross platform usability but research suggests that Windows occupies more than 90% of the  Australian market so there is no need to be fussy about cross plateform.

I know that this question is a bit vague. My apology, at this stage I am still brainstorming.

Question by:Sheils
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
LVL 10

Assisted Solution

by:Michael Vasilevsky
Michael Vasilevsky earned 540 total points
ID: 34931421
You'll need to supply your user's with a runtime version of Access. That's the only way they can run your application without an Access license. It's free to download:

I use Access runtime 2003 and compile an installation package using the Access 2003 Developer Extensions Package Wizard. It's really easy to use and adds a level of professionalism to your applications, but it does cost $. Details here:

Hope this helps!

LVL 16

Author Comment

ID: 34931535
Sounds like a good start.

I will just live this post open for another 24hr and see if there is any futher comments/advise

LVL 40

Assisted Solution

als315 earned 540 total points
ID: 34931921
In Access 2010 you have "Save and Publish" option, where is master for DB distribution. You can include runtime and prepare pack with your DB.
Survive A High-Traffic Event with Percona

Your application or website rely on your database to deliver information about products and services to your customers. You can’t afford to have your database lose performance, lose availability or become unresponsive – even for just a few minutes.


Expert Comment

ID: 34931997
A great tool here for deployment.

LVL 85

Accepted Solution

Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 720 total points
ID: 34932790
First and foremost: There are a lot of issues with deployment of Access applications, generally more so than deployment of apps using other languages (like VB.NET or VB6, for example). The need for the Runtime is the biggest issue, but there are ways around that. If you were just starting on your journey, I'd encourage you to consider using VB.NET to develop your application, but note that would require a steep learning curve in many cases.

With that said:

There are also a lot of "gotchas" with Runtime deployment. See these MSDN article for the details. Some of them are for different versions of Access, but the content is still relevant:

Developing Access Runtime Applications

Deploying Complex Microsoft Office Access Runtime-Based Solutions:

I'd also encourage you to thoroughly test your application on ALL common platforms (i.e. Windows XP/Vista/Win7 (32 and 64 bits)). At this stage of the game an MSDN subscription is invaluable to you, since it provides you with numerous license keys for all those Operating systems. Using "virtual machine" software, like vmWare or VirtualPC. With this software, you can build virtual machines that allow you to exactly emulate your end user environments. This is invaluable for troubleshooting deployment issues, since what works great on a Windows XP SP3 machine doesn't necessarily work on a Windows XP SP2 machine - and if you can't emulate that environment, your support troubles will quickly sink your reputation.

Do you have a compiled help file with context-sensitive help? That's a requirement for a commercially-distributed application, and users will expect it. Here's some good links regarding this:

Using HTML Help with Access:

Tony Toews site page regarding Access help:

I use Help and Manual to do this: It's easy to use and produces excellent results. I've also used WestWind ( and HelpStudio ( Both of those work well also.

I too highly recommend Sagekey for your deployment needs, especially when you're deploying the Runtime with your package. Without it, you can get some very irate customers. As you may be aware, if you have other versions of Access on the machine, Access will "register" the last used version and use that when the user doubleclicks a .mdb file, for example. This means that if you install the runtime, and the user launch your app, the NEXT time they fire off an Access application using just a doubleclick, that file will open in the Runtime, and in most cases that is NOT what the enduser expected. Sagekey includes a utility that ensures your application launches using the Runtime, but when your app has finished loading it reverts the machine back to the way it was prior to your app running - which means that the end user is happy, and you don't get nasty support calls!

Sagekey also doubles as a professional installer, so your enduser has a positive impression of your app.

LVL 58

Assisted Solution

by:Jim Dettman (Microsoft MVP/ EE MVE)
Jim Dettman (Microsoft MVP/ EE MVE) earned 200 total points
ID: 34932986

  I would also kick in that the runtime is free to distribute only with A2007 and up.   A2003 would cost $$.

  Also, you can check your app using a full version to see how it will behave in runtime mode by starting the full version with the /runtime switch.


<<At this stage I am open to suggestion the end result could be a browser based or exe application. Browser based will be better as it will provide cross platform usability but research suggests that Windows occupies more than 90% of the  Australian market so there is no need to be fussy about cross plateform.>>

   You can run Access based apps via a couple of different means:


2. Access 2010 and Sharepoint Access Services - Let's you run Access apps out of share point

3. Use of terminal server - This is really not a distribution option, but one more for a company that want's to run a Access app over a WAN.

  But there is no direct "conversion" to web enable an Access app or create an .EXE.

  Keep in mind that an Access app is more like a document that is read rather then a program that is executed.

LVL 16

Author Comment

ID: 34935400
Hi Guys

That's great a fair few thinks to chew on.

I will try the realtime option first and see how it works on my desktop which has office 2003 as oppose to my desktop which has office 2010.

I have downloaded the runtime.exe and installed it but I can't find where it runs from. But I guess that a separate question.
LVL 85
ID: 34937079
In generally installs in a folder under <Program Files>\Microsoft Office\<Your Version>, but I"m not sure on that. As JimD said, however, you can emulate the runtime by launching your application with the /runtime switch. The simplest way to do that is to build a desktop shortcut with a target like this:

"full path to msaccess.exe" "full path to your database" /runtime

And please - don't be fooled into thinking that if it runs okay on your machine with multiple versions, that it will do so on other machines. The forums and newsgroups are full of postings where developers tried to simply deploy the Access runtime without using Sagekey, and none of them are positive :). That's not to say it can't happen - I'm sure it does, in tightly controlled environments where the devs can insure that ALL processes are launched with the correct version of Access, and there is sufficient training and such so that the users aren't overburdened with the long delay that can come about when switching versions. However, if you're deploying "in the wild", you won't have that control, and it's incumbent on you to take every precaution to avoid that.

LVL 16

Author Comment

ID: 34938310
Thanks LSM

I do intend to use SageKey when I am ready to deploy, which will probably be 1yr from know. For know I am just looking for options that sounds promising.

For know I will just have a play with runtime on my own computer using some dummy application. Then I will develop the actual application and involve Sagekey.

Thanks Again


Featured Post

The top UI technologies you need to be aware of

An important part of the job as a front-end developer is to stay up to date and in contact with new tools, trends and workflows. That’s why you cannot miss this upcoming webinar to explore the latest trends in UI technologies!

Question has a verified solution.

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

Invest in your employees with these five simple steps to improve employee engagement and retention.
We live in a world of interfaces like the one in the title picture. VBA also allows to use interfaces which offers a lot of possibilities. This article describes how to use interfaces in VBA and how to work around their bugs.
With the power of JIRA, there's an unlimited number of ways you can customize it, use it and benefit from it. With that in mind, there's bound to be things that I wasn't able to cover in this course. With this summary we'll look at some places to go…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

705 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