tags:

views:

496

answers:

6
+3  Q: 

access 2007 to exe

Good day, made a database in ms access 2007 with forms, I need to create a stand alone exe file from access, is it possible? if yes. how?

thanks a mil

A: 

no it's not possible.

Time Machine
Literally speaking, no (i.e., no EXE). Practically speaking, the runtime does the job.
David-W-Fenton
A: 

I don't believe it is possible. Sorry to say. You need the Access to launch and display the form.

But you can use a runtime.
Tony Toews
A: 

If you have the Developer version of MS Access, you can create an '.mde' file, which operates just like an .exe file as far as your user is concerned. Essentially, creating an .mde wraps a version of the MS Access run-time along with your database.

As long as you have done a decent job with your form design, the user really can't tell the difference between your .mde file and a .exe.

I haven't used the Developer version in a number of years, but if I recall, it is quite expensive. EDIT (It appears to be free these days).

Here is a link to a good FAQ on the topic. Much more up-to-date than my recollections from the past.

Stewbob
I thought you had to distribute the runtime separately - the MDE is just a MDB without the readable code.
DJ
The Developer Edition was never expensive. It was a set of tools available as an upgrade for around $300. If you were replacing 3 standalone full Access installations with the runtime, you would have broken even.
David-W-Fenton
The Developer Eition is not required to create an MDE. These are two separate and distinct thing.
Tony Toews
An MDE is pretty far from an EXE file considering it requires Access to run it.
JohnFx
+3  A: 

You can't save it as .exe, but you could use the Access Runtime to allow users without Access to use your Application.

Michael Stum
+3  A: 

If I can just add my two cents worth...

You DO have to distribute the Access runtimes with your application. I heard recently on Stackoverflow on a questions that Microsoft runtimes for access are now freely downloadable.

Here are a couple of links...

http://www.granite.ab.ca/access/developeredition2007faq.htm
http://blogs.msdn.com/clintcovington/archive/2007/01/30/the-runtime-and-developer-extensions-will-be-free.aspx

You can either distribute these runtimes with your application or you can have your customer download them.

EDIT - THE BELOW IS PROVEN FALSE. YOU DO NOT HAVE TO PURCHASE A LICENSE TO DISTRIBUTE THE RUNTIMES. Of course, they are distributed under a license but the license is free. I leave the comment below for its historical interest.
I think but am not sure that to distribute the access runtimes with your application you will have to have a license. I know that you used to get this license with an MSDN subscription and with Visual Studio Tools for Office.
END FALSEHOOD

Once you have the Access Runtimes, you can create BULLETPROOF runtime installations of Access apps using preconfigured installation scripts from SageKey.com.

Office developer tools comes with some deployment options but they are not bulletproof and I would NEVER distribute a commercial application using those...they just don't work. But the sagekey scripts absolutely ROCK. They work incredibly well.

All this presumes you want to widely distribute your app. If not (for example...you want to just deploy to your customers and you will have complete control over that) then you can use the download from Microsoft option mentioned above.

One last thing. Runtime access apps have to be VERY robust. You have to do error handling and automatic table linking very well among other things or you will spend all the time on the phone with your customers rather than selling/distributing software.

Hope this helps.

Seth

Seth Spearman
Your last paragraph says it all. It's why I don't do those kind of apps anymore. +1
Stewbob
There are not "runtimes", only the Access Runtime. It is freely distributable without any licensing beyond what you have to click through to install it.
David-W-Fenton
David,Can you point to a web page that says that the runtimes are "freely distributable". Freely distributable and freely downloadable are not necessarily the same thing.Seth
Seth Spearman
Actually,I would still do a lot of research if before I would deploy with them, but I think ARE freely distributable which is pretty incredible.Seth
Seth Spearman
Stewbob. Even if you're not using a runtime you should still be doing error handling. If you're working on your own corporate systems then the automatic table linking isn't required so long as you are handling that scenario yourself.
Tony Toews
Seth. From Clint's blog article in your posting. "You can freely redistribute it or just point people to the download on icrosoft.com"
Tony Toews
Tony,I admit I scanned the page instead of thoroughly reading it. I think I will update my post to reflect this fact. Good catch.Seth
Seth Spearman
+1  A: 

As far as bullet proof runtimes yes Sagekey is an answer. However another alternative is Albert Kallal's Inno script which checks to see if a version of Access is installed. If not it tells you to install a runtime version of Access. If installed then it continues to install your FE MDE and other assorted files. http://groups.google.com/group/microsoft.public.access/msg/10e3fc9234660872?hl=en

Sample inno script which "wraps" the package wizard install into a single .exe http://groups.google.com/group/comp.databases.ms-access/msg/4aa1b33a191bf1f8?hl=en

Deploying updates to your software in a Runtime environment for Access 2007 http://www.members.shaw.ca/AlbertKallal/RunTime/InstallExample.htm

The only scenario which it wouldn't handle well would be if the user does install Access or a different Access runtime on their system later. However if you ship your product in Access 2000 format the problems are minimized.

Tony Toews
Tony,It is great to know about a strong free product that does the runtimes for you. For the record, though, when I say the sagekey scripts are bulletproof I mean exactly that they are impervious to the user installing other version of access or office...which in a truly widely distributed access runtime app is critical.Even with that said...the sagekey scripts ARE expensive...and (heres the rub) do NOT even include the actual installer engine like Wise or Installbuilder which if you add to the cost are VERY HEFTY. So good heads up on a cheaper alternative.Seth
Seth Spearman
Seth, apparently now the Sagekey scripts do some with their own installer.
Tony Toews