Question : CAB (inside MSI) files Vs EXE file

I am creating an installation package for my MS Access database.

I have a choice of creating either a MSI package or single compressed EXE file.  To date, I have been creating an EXE file, that I upload to our web-server, send the hyperlink to the client. which they can then run from either the webserver or download and run locally.  So far this has not caused me any issues, but I am no Network Manager and I need to get this right.

Thanks as always.

Answer : CAB (inside MSI) files Vs EXE file

EXE files are the preferred method for installing our software, as they are able to detect an existing version of the software and offer the user the option of uninstalling the existing product. MSI files do not have this ability and will instruct the user to use the Add/Remove Programs on the Control Panel to remove the existing product first.

In many situations, the EXE packaging combined with pre-configured command-line options would be sufficiently error-proof, especially if /qb is used.  The /qb option has the often-desirable effect of eliminating dialogs from the GUI that enable the user to override how the product is installed.

The only problem with using the EXE arises when you need to deploy an unattended installation/upgrade.  There is no way to instruct the EXE to uninstall the existing version without first prompting the user.  
Random Solutions  
 
programming4us programming4us