Packaging Wizard - Change Root Installation Folder

[theprez]

I am using the Packaging Wizard of the MS Office Access 2003 Developer Extensions. I would like to change the Root Installation folder to a customer Folder. However, I am limited to the list given (Program Files, Documents & Settings, etc..). I even tried to see if I could change the INI files produced by the package, but could not find any reference to the root installation folder. Does anyone know how to change this, either through the wizard or manually.

I know I can have the user move the folder once the install is complete, but I do not with to do this.

 

[ghudson]

I never found a way to do it either.

If your users already have Access 2003 installed then you can easily give them a self-extracting WinZip file to place the db files where ever you want. Include a custom shortcut that the user has to use to open your db with the /Runtime switch.

If the users do not have Access 2003 installed then create a generic runtime installation that gets installed to the users Program Files directory. Then also include a self-extracting WinZip file to place the db files where ever you want. Again, include a custom shortcut that the user has to use to open your db with the /Runtime switch.

That is how I over came the Access 2003 runtime packing limitation.

 

[WindSailor]

I am sorry, but I think I may have miss understood this, but I can create a new custom folder in any folder using the "browse" button when chosing the destination.
So I can basically install it anywhere and make a custom folder using the "New Folder" option.

If your talking about splitting the components up and installing them in seperate folders within the wizard, sorry.

Which brings up the question what packaging app do you guys prefer?

What root folder do you prefer (some prefer program files, others prefer ALL Users)?

The only thing I have read on other forums about installing the runtime version, is not to install it in the same folder as the full version of Access if it is installed on that computer.

I have a question about the "/runtime" switch; in the past when I have created a MDE and distributed it with the runtime version along with the shortcut to the database, I did not check the "/runtime" option on the "Additional parameters" page when creating the package and the database would run fine. Actually the database threw an error, one I didn't catch, and the app didn't crash (just acknowledged the error, and it moved on).
They did not have the full version of Access installed on that computer.

Is checking the "/runtime" switch absolutely necessary?

Any other info would be great!

Thanks

 

[theprez]

Packaging Wizard

I prefer the 2000 Packaging wizard. Seems to have much more flexibility. For now I may try to create a bat file to move the folder from the program files folder to a higher level. If this works the only thing the user will need to manually change is the shortcut.

 

[theprez]

I decided to go with a suggestion from WindSailor. I documented the process very carefully for users performing the install. I instructed to use the Custom option, instead of the Typical setup. In custom, there is an option to select the destination folder. Here is where I instructed the user to type in the exact path/folder I wanted, which is not fully available in the packaging wizard.