I never spent the time, but presubnlby, you can change the Product code
(on page 5 of 7 in the wizard). Simply delete the upgrade code, and then tab
out of the field..and then tab back in...(you get a new code).
This will allow you to install "again" on the target machine. However, if
you don't first delete the target mde file, then it will NOT copy over. The
lack of ability to copy "over" an existing mde file makes the wizard useless
for upgrades. You would have to have users first un-install existing.
However, I would not actually attached, or package the mde your distribution
with the runtime anyway.
I would create two separates installs.
My first install would simply install he runtime ONLY. (use package wizard).
Then, for additional installs, I would simply then send the customer a
zipped mde. They are REALLY small. However, since the customer can't know
where to pt the mde, then I would use a free installer (I use inno).
You could use the package wizard as mentioned, as thus your 2nd install
would be separate, and you could thus un-install the original.
So, split the install into two parts. It makes ZERO sense to send a customer
a 34 meg for a upgrade WHEN YOU KNOW they already have the runtime
installed.
Further, if you use a free tool like inno, then you can create a single .exe
file for the install (as opposed to a folder like the package wizard).
By having a simple single file for upgrading, then you can email this file,
or even just place it on your web space as a link, and they can upgrade that
way. In fact, if you have a web link, then it is about 2 lines of access
code to upgrade.
I actually grabbed the ftp code from
www.mvp.org/access, and created a
button:
Here is some screen shots of how my customers upgrade their ms-access to the
latest version:
http://www.kallal.ca/ridestutorialp/upgrade.html
And, a zipped mde file is going to be like maybe a 1 meg, or 2....about
10-20 seconds download on a internet tops.
Further, since you MUST be running a split database, then you already have a
environment in which separate pieces need be installed. (you are running a
split environment..right?? -- else how could you be upgrading the users in
the field???).
So, you need to sepeate the two parts. The ms-access isntaller has upgrade
and product code settings in the wizard, but you can't really use these
features becuase you can NOT over write existing mdb/mde files on your
comptuer.
So, I would *just* use the package wizard to install the runtime. after
htat, use the free inno installer here to instll your front end (or program
part).
And, the nice part to boot is if the customer already has ms-access, then
your install is going to be tiny..and they don't have to bother with the
runtime.
Inno is free, and can be found here:
http://www.jrsoftware.org/isinfo.php
here is simple sample inno script:
[Setup]
SourceDir=c:\Documents and Settings\All Users\Application Data\RidesL
AppName=Rides Reservation System
AppVerName= Rides 2.0
DefaultDirName={commonappdata}\RidesL
DefaultGroupName=Rides
Compression=lzma
SolidCompression=yes
DirExistsWarning=no
DisableDirPage=yes
DisableProgramGroupPage=yes
Uninstallable=no
[Files]
Source: "RidesXP.mde"; DestDir: "{app}"
[Icons]
Name: "{group}\Rides (Stampede Reservations)"; Filename:
"{app}\RidesXP.mde"; IconFilename: "{app}\cowboy.ico"; comment: "Starts the
Rides Booking System"
Name: "{userdesktop}\Rides (Stampede Reservations)"; FileName: "C:\Program
Files\Microsoft Office\OFFICE11\MSACCESS.EXE"; IconFilename:
"{app}\cowboy.ico"; comment: "Starts the Rides Booking System"
[Registry]
Root: HKLM; Subkey: "SOFTWARE\Microsoft\Jet\4.0\Engines"; ValueType: dword;
ValueName: "SandBoxMode"; ValueData: "2"
Root: HKLM;Subkey:
"Software\Microsoft\Office\11.0\Access\Security";ValueType: dword;
ValueName: "Level"; ValueData: "1"
Note how I have to two reg keys to elimonate hte marcor nag prompts.