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

Lauren Wilson wrote:[color=blue]
> 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.[/color]

This might get you up and running in the short term. The Package &
Deployment Wizard creates an INI file called SETUP.LST, that SETUP.EXE
uses to run the installation. You can edit the LST file to specify a
different install path than the one that the Wizard wrote.

The section in the file is [Setup] and the key is DefaultDir.