I have a desperate short term need for a way to install Access 2003
runtime on client computers. I have the proper license to do so but I
cannot seem to find the files to do it like we did with the old Access
2000 Runtime. Also, I cannot use the MS Package & Deployment wizard
because it won't allow us to install our app into the specific path
that it must be in. It only seems to allow preset macros to define
the target install path -- none of which will work for our app.

The short term solution is simply to install Access 2003 Runtime with
a separate install package.

Ultimately, we'll do it with a Wise install package. But that's a
whole Usenet group in itself and a lot of work for our app. We're
developing that now but we have beta testers who need Access 2003 NOW
and we don't want to force them to buy it.

Any advice?

Thanks folks.

-- LW

> Deployment wizard
because it won't allow us to install our app into the specific path
that it must be in.

Hum..the package wizard on 2 of 7 allows you to choose the common settings
where your application should be installed.

They are:
Desktop, program files, Common App Data etc.

I can't imagine why you would want to install to anywhere else then those
above common directories. The options for the
target directory where your appcation installs is plenty covered by the
options given above. I see no reason why
you say you have no control as to where you application goes.
[color=blue]
>The short term solution is simply to install Access 2003 Runtime with[/color]
a separate install package.

Yes...the location of the runtime certainly can't be chosen. (but...who
cares.??? why does it matter?). To be sure, the a2003 p & d does use
whatever directory the user installed office to. And, if the location of the
directory is non standard, then it is true that the p & w CREATES WRONG
shortcuts. This is exactly why I had to dump the p & d for the a2003.

In fact, what I do is simply package the a2003 runtime with the p & d, and
then build my OWN install using iiino. The reason for this is that upgrades
are easer to do..and further, the shortcuts are correct....

So, just build the runtime install with the p & d as per above.

At this point, you now can use one of many installers to simply setup you
mde file. Remember, once the runtime is installed, then all you really have
to do is "copy" your mde file tot he users copter..and it will work. There
is noting "special" you have to do here..and it is a just a plane Jane mde
file as usual.

If things were simple..then you could use www.winzip.com.

I used to use the above WinZip for a consider amount of time (if you
registered WinZip for a very low fee..it will create self extracting zip
files for you).
After all...usually the only thing I needed to do was un-zip a mde file to a
particular directory.

So, once you have the runtime installed using the p & d...for deployment of
the mde..and building shortcuts etc....just use something else.

The best approach I found is to use the free Inno installer. It really is
nice..and is easy to use. (and it is free). And, since these innno scripts
really only have to install a mde file..and setup a few shortcuts for
you...they are very easy to write.

you can find the free inno installer here:

http://www.jrsoftware.org/isinfo.php

I highly recommend using the inno for installing your mde files and setting
up shortcuts. And, I see no reason not to continue to use the access 2003
and the package wizard to deploy the runtime part...

If you *really* must change the location as to where the runtime
installs..then you can purchase some scripts here:

www.sagekey.com


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.members.shaw.ca/AlbertKallal

Thanks Albert. Obviously, I blurred the distinction between our need
to install ART 2003 and the actual app. We must install the APP
itself to a specific, hard coded location for security reasons I am
not allowed to reveal, but the location of ART is irrelevant, as long
as it works.

I'm embarrassed to admit I did not think of using the P & D Wizard to
install just ART.


On Tue, 24 Jan 2006 11:44:54 GMT, "Albert D. Kallal" <kallal@msn.com>
wrote:
[color=blue][color=green]
>> Deployment wizard[/color]
>because it won't allow us to install our app into the specific path
>that it must be in.
>
>Hum..the package wizard on 2 of 7 allows you to choose the common settings
>where your application should be installed.
>
>They are:
> Desktop, program files, Common App Data etc.
>
>I can't imagine why you would want to install to anywhere else then those
>above common directories. The options for the
>target directory where your appcation installs is plenty covered by the
>options given above. I see no reason why
>you say you have no control as to where you application goes.
>[color=green]
>>The short term solution is simply to install Access 2003 Runtime with[/color]
>a separate install package.
>
>Yes...the location of the runtime certainly can't be chosen. (but...who
>cares.??? why does it matter?). To be sure, the a2003 p & d does use
>whatever directory the user installed office to. And, if the location of the
>directory is non standard, then it is true that the p & w CREATES WRONG
>shortcuts. This is exactly why I had to dump the p & d for the a2003.
>
>In fact, what I do is simply package the a2003 runtime with the p & d, and
>then build my OWN install using iiino. The reason for this is that upgrades
>are easer to do..and further, the shortcuts are correct....
>
>So, just build the runtime install with the p & d as per above.
>
>At this point, you now can use one of many installers to simply setup you
>mde file. Remember, once the runtime is installed, then all you really have
>to do is "copy" your mde file tot he users copter..and it will work. There
>is noting "special" you have to do here..and it is a just a plane Jane mde
>file as usual.
>
>If things were simple..then you could use www.winzip.com.
>
>I used to use the above WinZip for a consider amount of time (if you
>registered WinZip for a very low fee..it will create self extracting zip
>files for you).
>After all...usually the only thing I needed to do was un-zip a mde file to a
>particular directory.
>
>So, once you have the runtime installed using the p & d...for deployment of
>the mde..and building shortcuts etc....just use something else.
>
>The best approach I found is to use the free Inno installer. It really is
>nice..and is easy to use. (and it is free). And, since these innno scripts
>really only have to install a mde file..and setup a few shortcuts for
>you...they are very easy to write.
>
>you can find the free inno installer here:
>
>http://www.jrsoftware.org/isinfo.php
>
>I highly recommend using the inno for installing your mde files and setting
>up shortcuts. And, I see no reason not to continue to use the access 2003
>and the package wizard to deploy the runtime part...
>
>If you *really* must change the location as to where the runtime
>installs..then you can purchase some scripts here:
>
>www.sagekey.com[/color]

Well, I have now tried this. The P & D Wizard that comes with Office
2003 Dev Ext. will not allow me to create an install package that only
includes ART 2003. It MUST include a "valid" Access MDB or MDE or
Project file. Back to square 1.

Any other ideas? Or am I overlooking something




On Tue, 24 Jan 2006 11:21:35 -0600, Lauren Wilson <nospam@nospam.com>
wrote:
[color=blue]
>Thanks Albert. Obviously, I blurred the distinction between our need
>to install ART 2003 and the actual app. We must install the APP
>itself to a specific, hard coded location for security reasons I am
>not allowed to reveal, but the location of ART is irrelevant, as long
>as it works.
>
>I'm embarrassed to admit I did not think of using the P & D Wizard to
>install just ART.
>
>
>On Tue, 24 Jan 2006 11:44:54 GMT, "Albert D. Kallal" <kallal@msn.com>
>wrote:
>[color=green][color=darkred]
>>> Deployment wizard[/color]
>>because it won't allow us to install our app into the specific path
>>that it must be in.
>>
>>Hum..the package wizard on 2 of 7 allows you to choose the common settings
>>where your application should be installed.
>>
>>They are:
>> Desktop, program files, Common App Data etc.
>>
>>I can't imagine why you would want to install to anywhere else then those
>>above common directories. The options for the
>>target directory where your appcation installs is plenty covered by the
>>options given above. I see no reason why
>>you say you have no control as to where you application goes.
>>[color=darkred]
>>>The short term solution is simply to install Access 2003 Runtime with[/color]
>>a separate install package.
>>
>>Yes...the location of the runtime certainly can't be chosen. (but...who
>>cares.??? why does it matter?). To be sure, the a2003 p & d does use
>>whatever directory the user installed office to. And, if the location of the
>>directory is non standard, then it is true that the p & w CREATES WRONG
>>shortcuts. This is exactly why I had to dump the p & d for the a2003.
>>
>>In fact, what I do is simply package the a2003 runtime with the p & d, and
>>then build my OWN install using iiino. The reason for this is that upgrades
>>are easer to do..and further, the shortcuts are correct....
>>
>>So, just build the runtime install with the p & d as per above.
>>
>>At this point, you now can use one of many installers to simply setup you
>>mde file. Remember, once the runtime is installed, then all you really have
>>to do is "copy" your mde file tot he users copter..and it will work. There
>>is noting "special" you have to do here..and it is a just a plane Jane mde
>>file as usual.
>>
>>If things were simple..then you could use www.winzip.com.
>>
>>I used to use the above WinZip for a consider amount of time (if you
>>registered WinZip for a very low fee..it will create self extracting zip
>>files for you).
>>After all...usually the only thing I needed to do was un-zip a mde file to a
>>particular directory.
>>
>>So, once you have the runtime installed using the p & d...for deployment of
>>the mde..and building shortcuts etc....just use something else.
>>
>>The best approach I found is to use the free Inno installer. It really is
>>nice..and is easy to use. (and it is free). And, since these innno scripts
>>really only have to install a mde file..and setup a few shortcuts for
>>you...they are very easy to write.
>>
>>you can find the free inno installer here:
>>
>>http://www.jrsoftware.org/isinfo.php
>>
>>I highly recommend using the inno for installing your mde files and setting
>>up shortcuts. And, I see no reason not to continue to use the access 2003
>>and the package wizard to deploy the runtime part...
>>
>>If you *really* must change the location as to where the runtime
>>installs..then you can purchase some scripts here:
>>
>>www.sagekey.com[/color][/color]

Lauren Wilson a scris:[color=blue]
> Well, I have now tried this. The P & D Wizard that comes with Office
> 2003 Dev Ext. will not allow me to create an install package that only
> includes ART 2003. It MUST include a "valid" Access MDB or MDE or
> Project file. Back to square 1.
>
> Any other ideas? Or am I overlooking something
>
>[/color]
Well then include a dummy mde or mdb files.

Sebastian

You really don`t need the P&D Wizard that comes with Office to install
only ART 2003. You will find the msi installer of ART 2003 in
'\Files\Accrt\Accessrt.msi' on your Office 2003 CD. Then as Albert said
you can use a installer (Inno installer is the best you can get for
free) to install your specific app files.

Sebastian

Lauren Wilson wrote:[color=blue]
> I have a desperate short term need for a way to install Access 2003 runtime on client
> computers.
> I cannot use the MS Package & Deployment wizard because it won't allow us to install our
> app into the specific path that it must be in. It only seems to allow preset macros to define
> the target install path -- none of which will work for our app.
> The short term solution is simply to install Access 2003 Runtime with a separate install
> package.[/color]

Lauren, I recommend Agentix Installer: http://www.aginstaller.com
for building install package for the runtime.

It allows you to choose the specific path where your application should
be installed, works on all versions of Windows, creates a single-exe
setups, supports multilingual installations and has a complete set of
the gentleman's features - shortcuts creation, creation of registry and
..INI entries and more. It has it's own scripting mechanism, but it's
more easy to learn and use.

It is very impressive, doing almost everything Inno Setup does, but
producing setup files 250-290Kb smaller because of the very low (48Kb
only) overhead. It is not free, but is reasonably priced.

Lauren Wilson wrote:[color=blue]
> I have a desperate short term need for a way to install Access 2003 runtime on client
> computers.
> I cannot use the MS Package & Deployment wizard because it won't allow us to install our
> app into the specific path that it must be in. It only seems to allow preset macros to define
> the target install path -- none of which will work for our app.
> The short term solution is simply to install Access 2003 Runtime with a separate install
> package.[/color]

Lauren, I recommend Agentix Installer: http://www.aginstaller.com
for building install package for the runtime.

It allows you to choose the specific path where your application should
be installed, works on all versions of Windows, creates a single-exe
setups, supports multilingual installations and has a complete set of
the gentleman's features - shortcuts creation, creation of registry and
..INI entries and more. It has it's own scripting mechanism, but it's
more easy to learn and use.

It is very impressive, doing almost everything Inno Setup does, but
producing setup files 250-290Kb smaller because of the very low (48Kb
only) overhead. It is not free, but is reasonably priced.

Thanks Alexey! I'll check it out. We actually already spent about
$1000 on a combination of SageKey scripts and the Wise Installer
package. Eventually I'll manage to wade through it. In the mean time,
I need a quick, "down and dirty" install builder that I can use to
whip together an installer for JUST Access 2003 Runtime. Perhaps this
is the one.


On 2 Feb 2006 17:01:45 -0800, "Alexey Gousev" <algous@gmail.com>
wrote:
[color=blue]
>Lauren Wilson wrote:[color=green]
>> I have a desperate short term need for a way to install Access 2003 runtime on client
>> computers.
>> I cannot use the MS Package & Deployment wizard because it won't allow us to install our
>> app into the specific path that it must be in. It only seems to allow preset macros to define
>> the target install path -- none of which will work for our app.
>> The short term solution is simply to install Access 2003 Runtime with a separate install
>> package.[/color]
>
>Lauren, I recommend Agentix Installer: http://www.aginstaller.com
>for building install package for the runtime.
>
>It allows you to choose the specific path where your application should
>be installed, works on all versions of Windows, creates a single-exe
>setups, supports multilingual installations and has a complete set of
>the gentleman's features - shortcuts creation, creation of registry and
>.INI entries and more. It has it's own scripting mechanism, but it's
>more easy to learn and use.
>
>It is very impressive, doing almost everything Inno Setup does, but
>producing setup files 250-290Kb smaller because of the very low (48Kb
>only) overhead. It is not free, but is reasonably priced.[/color]

Never mind. I figured it out.


On Thu, 02 Feb 2006 19:38:39 -0600, Lauren Wilson <nospam@nospam.com>
wrote:
[color=blue]
>Thanks Alexey! I'll check it out. We actually already spent about
>$1000 on a combination of SageKey scripts and the Wise Installer
>package. Eventually I'll manage to wade through it. In the mean time,
>I need a quick, "down and dirty" install builder that I can use to
>whip together an installer for JUST Access 2003 Runtime. Perhaps this
>is the one.
>
>
>On 2 Feb 2006 17:01:45 -0800, "Alexey Gousev" <algous@gmail.com>
>wrote:
>[color=green]
>>Lauren Wilson wrote:[color=darkred]
>>> I have a desperate short term need for a way to install Access 2003 runtime on client
>>> computers.
>>> I cannot use the MS Package & Deployment wizard because it won't allow us to install our
>>> app into the specific path that it must be in. It only seems to allow preset macros to define
>>> the target install path -- none of which will work for our app.
>>> The short term solution is simply to install Access 2003 Runtime with a separate install
>>> package.[/color]
>>
>>Lauren, I recommend Agentix Installer: http://www.aginstaller.com
>>for building install package for the runtime.
>>
>>It allows you to choose the specific path where your application should
>>be installed, works on all versions of Windows, creates a single-exe
>>setups, supports multilingual installations and has a complete set of
>>the gentleman's features - shortcuts creation, creation of registry and
>>.INI entries and more. It has it's own scripting mechanism, but it's
>>more easy to learn and use.
>>
>>It is very impressive, doing almost everything Inno Setup does, but
>>producing setup files 250-290Kb smaller because of the very low (48Kb
>>only) overhead. It is not free, but is reasonably priced.[/color][/color]

Lauren Wilson wrote:[color=blue]
> Thanks Alexey! I'll check it out.
> In the mean time, I need a quick, "down and dirty" install builder that I can use to
> whip together an installer for JUST Access 2003 Runtime. Perhaps this
> is the one.[/color]

If you need a help of creating a setup script for the Access 2003
Runtime installer feel free to contact me.