upgrade package solution

[tadropik]

I would like to make an Access 2007 application available to my clients via a web download.

Some have Access installed, other do not.

So I have used the Package Solution wizard to make an Installation package which also deploys the access runtime.

I'm able to Zip all neccessary files to a .exe allowing them to download the exe and automatcially run the setup.exe.

All is Great, right?

Yes, for those downloading for the first time.

When I make functional upgrades, the installation package requires them to uninstall the previous version before installing the new version.

I want the upgrade to be a seemless function. Which is to say I'd like the
install to simply over write the existing application.

Can this be done?

New Clients and existing Clients will be downloading the intall package.
So I can see having 2 seperate links on the web site where 1 is for new clients that downloads the install package and another that would simply download the update .mdb.

However, I'd like to get away with having only one download link.

 

[Dairy Farmer]

Download Runtimes and Developer (free from Microsoft)

With the release of Microsoft Office Access 2007, the Access 2007 Developer Extensions and the Access 2007 Runtime are available as free downloads. These utilities provide database developers with tools to package and deploy a database, create database templates, and integrate a database with source code control systems, such as Microsoft Visual SourceSafe.

Developer will make install packages for you. It has 3 options:

1. Requires Access 2007 to be installed.

2. Requires Access 2007 Runtime to be downloaded if Access is not installed.
(The file will be installed with the ACCDR file extension and Access 2007 Runtime Support will be enabled.)

3. Requires nothing and install Access 2007 Runtime.
(The file will be installed with the ACCDR file extension and Access 2007 Runtime Support will be enabled.)

Use option 3 for new users.
Used doesn't need to download anything.
DB is installed as ACCDR.
Runtimes are always used for this file.

Use option 2 for updates.

 

[Dairy Farmer]

Sorry keep getting disconnected while editing.

Make sure you always save your DB as ACCDR. That way, even if they have Access the DB will always open with Runtime.

You could also use one of the free installer packages available that has the otion to act on registry values.
Make a Developer installer for new users.
Also create an ACCDR with the updated DB.

Next create an install package using one of the free install apps.
You want to read the registry.
If MyApp/version is missing then install full Developer package and write to registry MyApp/version/0.2.
If MyApp/version <>0.2 then install update DB and change registry to 0.2

 

[Dairy Farmer]

http://www.createinstall.com/ allows you to run a macro based on a registry value.

 

[tadropik]

CreateInstall works Great. It does everyting I want to.
It even runs the access application after it installs it.

However...
Some of my clients are running Access 2007, others are running Acess 2003.

in the "Run Application" portion of the CreateInstall I put in the path to MSACCESS.EXE in teh Filname. It works great. However the path to the right MSACCESS.EXE depends on which version of Access they have.

I wonder if I can do something in CreateInstall to tell me which version of Access they have?

 

[Dairy Farmer]

Package you app as a 2007 or 2010 Runtime. That way it doesn't matter which version of Access they have, or even if they don't have Access.