After days if not weeks of searching the WEB I have returned here. I am tiring to deploy an Access application using a MSI file. Most, but not all machines will have a copy of Access with various versions already installed. I have created a MSI using A2007 developer and have WinINSTALL to edit it with. A2007 runtime always wants to install. I need to make A2007 runtime to be optionally installed. This is because A2007 runtime causes havoc with computers that have Access 2000-2003 installed. Can anyone help with making MSI packages?
Question Creating MSI packages
- Thread starter wjburke2
- Start date
- Local time
- Today, 09:12
- Joined
- Feb 19, 2002
- Messages
- 47,035
Look into a product called SageKey. My client just bought it for me and I'm going to start using it on Monday. If everything they say is true, it will solve all your problems and then some.
Pat as usual I appreciate your advice. I have tried answering some posts and it takes real commitment to answer as many as you do. I have read through the information on the SageKey site. It alludes to it being able to coexist with all versions of Access. But then later it advises that you install with the version you developed in. I may try calling SageKey and see what it can do for us. I have tried several versions of Windows install software InstallTaylor, Orca, VERTAS, and WinInstall. Getting the company to shell out close to 1,000.00 for another will be a hard sell.
I am so close with my current package installer. I really only need it to deploy the MDB, create a desktop and menu item on most machines. Easy enough I just take out the chain install of 2007runtime in the setup.ini file. On the few machines that do not have any Access I need run the A2007runtime.exe. It would be nice to have the option to run A2007 runtime on the Install package setup menu. It would be even better if I could look at the programs\Microsoft directory and if Access is not there automatically run the A2007runtime. If I only understood INI script language better I feel there could be some conditional statements that would allow this.
I am so close with my current package installer. I really only need it to deploy the MDB, create a desktop and menu item on most machines. Easy enough I just take out the chain install of 2007runtime in the setup.ini file. On the few machines that do not have any Access I need run the A2007runtime.exe. It would be nice to have the option to run A2007 runtime on the Install package setup menu. It would be even better if I could look at the programs\Microsoft directory and if Access is not there automatically run the A2007runtime. If I only understood INI script language better I feel there could be some conditional statements that would allow this.
Nigel you make a good point, since we are just deploying there a lot of questions in that area. Plus patches going out all over the place. Which of course requires new installs. This is a Frount end application every user has a copy of the MDB on their machine the data is on a server. Our network guys a pretty good at getting around the install permisions so I don't think there is a problem there. They told me to get them a MSI and they would do the rest. I hope they are right.
Similar threads
