HI I have Access 2010 and have developed a program that I would like
to eventually install on a few users computers . The problem is their
computers don't have Access installed nor is it worth paying for the
program (for the little application I have). Someone told me there is
a way to install just the application on the computers without a full
blown version of access. Can someone explain to me how to do this?

Thanks
STeve

fishqqq (AT) hotmail (DOT) com wrote:

This might provide a start
http://www.microsoft.com/downloads/e...displaylang=en

If you are an experienced application developer, you can do this, but it
will need to be a "finished application" because the runtime does not allow
features that they consider "for developers", some of which are in rather
common use by end users.

If you have to hire an experienced developer (custom software work does not
come cheap), purchasing Office Pro for users who need the Access
functionality may be a less-expensive option.

Larry Linson
Microsoft Office Access MVP

<fishqqq (AT) hotmail (DOT) com> wrote

On Jan 31, 11:16*am, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
Thanks, - do i install the runtime program on the computer i've
created the application on - or do i install the runtime program on
the enduser's computer and xfer the .mdb file to that computer?

<fishqqq (AT) hotmail (DOT) com> wrote

On Jan 31, 11:16 am, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
..

Thanks, - do i install the runtime program on the computer i've
created the application on - or do i install the runtime program on
the enduser's computer and xfer the .mdb file to that computer?


You can install it on your own pc for testing. You also must install it on
each user's pc so they can run your mdb/mde. The desktop icon will have a
Target box (see the properties) and you reference the database from there.

You can test the runtime environment by staring full Access with the
/RUNTIME switch; you will also need to supply it the path to your
application.

wrote in message
news:93d94c40-7c78-413a-81ea-4d23f1804748 (AT) d1g2000yqb (DOT) googlegroups.com...

On Jan 31, 11:16 am, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
Thanks, - do i install the runtime program on the computer i've
created the application on - or do i install the runtime program on
the enduser's computer and xfer the .mdb file to that computer?

?"buckskin" wrote in message news:8qq19kFkruU1 (AT) mid (DOT) individual.net...

Yes, just install the runtime on the target computer. Then you can just copy
your access applications to that machine. When clicked on, they should run.

The only issue here is you need to provide a custom interface (so, startup
forms, and forms to launch reports etc. are required). So, as long as your
application provides the forms and menus, and the users don't need the
access interface, then you should be ok.

Note that for access 2010, the new security model means you can quite much
just install the runtime, and then copy your files, and they will run, the
only issue being is the first time a application is run, the user will be
nagged with a security prompt, but, this prompt only occurs once for each
application they answer yes to. This is much nicer then having to setup
trusted locations etc.

Also, as a general rule, installing the runtime on your computer is not
required, and in fact not even recommended. The installer is quite smart,
and if you already have a2010 installed, then the runtime really does not do
anything nor install access "over" your full version.

As a few noted, you need a test machine, or I recommend virtual pc or even
XP mode in windows 7 for testing of runtime. Another really good way to test
your application as runtime is to use the runtime switch mentioned elsewhere
in this thread. You MUST do some testing in runtime mode to see how your
application will run


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

"Albert D. Kallal" <PleaseNOOOsPAMmkallal (AT) msn (DOT) com> wrote

?"buckskin" wrote in message news:8qq19kFkruU1 (AT) mid (DOT) individual.net...




A good example of this is the code I had in my mdb

DoCmd.RunCommand acCmdSave

when I meant to write;

DoCmd.RunCommand acCmdSaveRecord


The first worked fine in the mdb and compiled into the mde. Though when I
ran the button containing that code in the mde under the runtime it crashed
and burned. During a demo.