HCS Consulting Group.
We make Complex Systems simple

Deploying updates to your software in a Runtime environment for Access 2007

By Albert D. Kallal
Friday, December 26,2008

Sample Install Page:

Step #1  - click here to download a zip file sample install of Super Easy Word merge

Step #2 - If you can't run the above install, please download a copy of the access runtime from here:

http://www.microsoft.com/downloads/details.aspx

------------

How the above was built:

Grab a free copy of the Inno installer from here:

http://www.jrsoftware.org/isinfo.php


Here is the sample install script used in the above:

 

; Script generated by the Inno Setup Script Wizard.
; SEE THE DOCUMENTATION FOR DETAILS ON CREATING INNO SETUP SCRIPT FILES!
 

[Setup]
AppName=Word Merge Example
AppVerName=Word Merge 2.0
AppPublisher=HCS Consulting Group

SourceDir=c:\WordMergeExample
DefaultDirName=c:\WordMergeExample
DisableDirPage=yes
DirExistsWarning=no
DefaultGroupName=Word Merge Example
DisableProgramGroupPage=yes
OutputBaseFilename=setup
Compression=lzma
SolidCompression=yes

[Files]
Source: "WordMerge07.accDB"; DestDir: "{app}"
Source: "WordMerge07_be.accDB"; DestDir: "{app}"; Flags: onlyifdoesntexist
Source: "merge.bmp"; DestDir: "{app}"

[Icons]
Name: "{userdesktop}\Word Merge Example"; FileName: "C:\Program Files\Microsoft Office\OFFICE12\MSACCESS.EXE"; Parameters: """{app}\WordMerge07.accDB"" /runtime"; IconFilename: "{app}\merge.bmp"; comment: "Word merge Example"
Name: "{group}\Word Merge Example"; Filename: "C:\Program Files\Microsoft Office\OFFICE12\MSACCESS.EXE"; Parameters: """{app}\WordMerge07.accDB"" /runtime"; IconFilename: "{app}\merge.bmp"; comment: "Word Merge Example"


[Registry]
Root: HKCU;Subkey: "Software\Microsoft\Office\12.0\Access\Security";ValueType: dword; ValueName: "VBAWarnings"; ValueData: "1"
 

All of this installing and "updating" idea assumes that your application has been split.

I explain in detail and here’s what I mean about splitting a database:

runtimeExample


And it would be wrong of me to ignore that there’s a significant number of compatibility issues when you attempt to run different versions of MS access on a target computer. Keep in mind because since we now realize that the runtime is much like a full version of access, then the "many" problems incompatibilities between having different versions of ms-access will continue to exist. I really don't recommend you install the runtime on an existing computer with a different version of ms-access. If you’re looking for large distribution and an commercial grade install f your application on the target computer with trouble free results, then about the only solution for this approach is to use a commercial installer with install scripts designed exactly for this purpose. For installing MS access there’s nobody better in our business then the people at Sagekey. You find out about their access install products here

www.sagekey.com
 

 

Back