By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,742 Members | 1,570 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,742 IT Pros & Developers. It's quick & easy.

Stand Alone Access Applications

P: n/a
What do I need to get (from Microsoft I assume) in order to distribute
stand alone Access applications to people who do not (and will not) have
Access installed on their systems?

I have heard about Run Time modules, but am unsure of what they are and
how they are obtained. Is there a cost associated with this?
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
fp
My information is relevant to AXP.

In what context do you want to distribute? Internal environment? External
environment? Retail sales? Enterprise Sales? Answering this question will
help you with an answer.

Do a search on this topic in this group and you will find your answer. From
what I remember, there is quite a bit of information about this very topic.

In short, you can use a developer version of office and get the packaging
wizard. This works for known distribution locations where you know what is
already there.

If you are real serious, use Wise or InstallShield and SageKey to distribute
your application. This works for locations where you have to install without
the knowledge of prior software installed.

--
******************************
Fred Parker
Lynn Consulting Group, L.L.C.
http://www.lynnconsultinggroup.com
******************************
Nov 12 '05 #2

P: n/a
On Fri, 06 Feb 2004 06:12:14 GMT in comp.databases.ms-access, "fp"
<et****************@hotmail.com> wrote:
My information is relevant to AXP.

In what context do you want to distribute? Internal environment? External
environment? Retail sales? Enterprise Sales? Answering this question will
help you with an answer.

Do a search on this topic in this group and you will find your answer. From
what I remember, there is quite a bit of information about this very topic.

In short, you can use a developer version of office and get the packaging
wizard. This works for known distribution locations where you know what is
already there.

If you are real serious, use Wise or InstallShield and SageKey to distribute
your application. This works for locations where you have to install without
the knowledge of prior software installed.


It shopuld be noted that in order to use InstallShield, etc, you still
need the office developer thingy in order to obtain both the runtime
version of Access and the licence to distribute it.

I'm guessing that nowadays you can only get the XP version (from MS)
so if you require an older version you can either use ebay to obtain
one or else (not sure if it still applies) get the latest version and
use the downgrade rights and a copy of the earlier one.

--
A)bort, R)etry, I)nfluence with large hammer.
Nov 12 '05 #3

P: n/a
Todd D. Levy wrote:
What do I need to get (from Microsoft I assume) in order to distribute
stand alone Access applications to people who do not (and will not) have
Access installed on their systems?

I have heard about Run Time modules, but am unsure of what they are and
how they are obtained. Is there a cost associated with this?

Probably nothing, to all your questions. I've deployed stand-alone
Access applications using ADO and it's pretty painless. You have to
make sure the target computer has MDAC installed. All Win2k+ computers
do but you'll probably want to distribute the latest version anyway.

You can get it here:
http://msdn.microsoft.com/downloads/...asp?frame=true

Nowdays I use Inno Setup for all my installation needs. Absolutely
free and incredibly easy to use compared to things like install
shield: http://www.jrsoftware.org/isdl.php

See the knowledge base article on installing MDAC:
http://www.jrsoftware.org/iskb.php

I don't know anything about run time modules. Others here can
answer that question.

Arvin
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.