More Packaging Problems

[Guest]

Hi,
I have an Access 2000 db that I'm trying to package with Office 2000
Developer. I want to package WITHOUT runtime. When I posted this before,
Paul gave me the info to package with runtime and then delete the Runtime
folder from my package and change the [Runtime] data in file setup.lst from
"Included=-1" to "Included=0". This worked on the computers that I have,
but when I tried to install my package on a computer with Access 2002 the Cab
fiels loaded and then I got a message somthing like "this program requires
Access, cannot continue with install..." and the setup program uninstalled
the already installed files. I created my own folder on the computer and
copied my frontend and backend db, created a shortcut to my db and everything
worked fine. Why won't the install package work?????? I'm not able to
package without run time and using Pauls trick I still have problems. There
is no way I can distribute my db with these packaging problems.

Any help would be appreciated.

 

[Paul Overway]

There are a number of problems with PDW generated installers. If you are
serious about distributing Access apps, the best thing you could do is
invest in a different installer. See whitepaper at web site below for some
suggestions.

 

[Albert D. Kallal]

I never did use the a2000 p&d. For the a2003 p&d, there is simply a check
box that says don't include the runtime, and that works rather well.

As mentioned, if you are not going to include the runtime, you can consider
editing the msi file with the free "Orca" tools from MS . (Orca is a install
script editor). The problem here is that the runtime scripts are HUGE.....

I would consider using Inno install. It is 100% free, and it is VERY nice.
Here is a install script to copy a few files...


; -- Example1.iss --
; Demonstrates copying 3 files and creating an icon.

; SEE THE DOCUMENTATION FOR DETAILS ON CREATING .ISS SCRIPT FILES!

[Setup]
SourceDir=c:\program files\stampede
AppName=Rides Stampede System
AppVerName= Rides 1.5
DefaultDirName={pf}\Stampede
DefaultGroupName=Rides
Compression=lzma
SolidCompression=yes

DirExistsWarning=no
DisableDirPage=yes
DisableProgramGroupPage=yes
Uninstallable=no


[Files]
Source: "cowboys.mde"; DestDir: "{app}"
Source: "cowboy.ico" ; DestDir: "{app}"
;Source: "MyProg.hlp"; DestDir: "{app}"
;Source: "Readme.txt"; DestDir: "{app}"; Flags: isreadme

[Icons]

Name: "{group}\My Program"; Filename: "{app}\cowboys.mde"; IconFilename:
"{app}\cowboy.ico"
Name: "{userdesktop}\My Program"; FileName: "{app}\cowboys.mde";
IconFilename: "{app}\cowboy.ico"

The above creates a program dir, install my mde, and the icon file, and then
makes shortcut on the desktop..and also in the start->Programs menu.

The other advantage of inno install is that you get ONE "setup.exe" file (as
opposed to autorun.inf, and "files folder" and setup.exe). I mean, sure, if
you are deploying to a cd, then the autorun stuff is nice. However, if you
are just going to email, or provide a download page to update/install the
files, then a single .exe file is far better.

Since you are not actually installing the runtime, then in effect you are
just copying a few files to the users computer. I would consider using Inno,
as it is free. You can go and get the orca tools, and start messing around
with LARGE scripts...but as you can see, the above script is rather small,
and the inno setup includes several "sample" scripts that you can modify
(that is what I did with the above).

 

[Guest]

Best regards to Albert Kallal:
I have Office 2003 Professional Edition and Visual Studio Tools for the
Microsoft Office System which includes Access Developer Extensions. My
intention is to distribute my microsoft access databases using the MSI hold
on ADE, but I wonder if the commented free installers Orca and INNO would
replace Sagekey Access 2003 Installer?
Many thanks,
Francisco from Mexico.

I never did use the a2000 p&d. For the a2003 p&d, there is simply a check
box that says don't include the runtime, and that works rather well.

As mentioned, if you are not going to include the runtime, you can consider
editing the msi file with the free "Orca" tools from MS . (Orca is a install
script editor). The problem here is that the runtime scripts are HUGE.....

I would consider using Inno install. It is 100% free, and it is VERY nice.
Here is a install script to copy a few files...


; -- Example1.iss --
; Demonstrates copying 3 files and creating an icon.

; SEE THE DOCUMENTATION FOR DETAILS ON CREATING .ISS SCRIPT FILES!

[Setup]
SourceDir=c:\program files\stampede
AppName=Rides Stampede System
AppVerName= Rides 1.5
DefaultDirName={pf}\Stampede
DefaultGroupName=Rides
Compression=lzma
SolidCompression=yes

DirExistsWarning=no
DisableDirPage=yes
DisableProgramGroupPage=yes
Uninstallable=no


[Files]
Source: "cowboys.mde"; DestDir: "{app}"
Source: "cowboy.ico" ; DestDir: "{app}"
;Source: "MyProg.hlp"; DestDir: "{app}"
;Source: "Readme.txt"; DestDir: "{app}"; Flags: isreadme

[Icons]

Name: "{group}\My Program"; Filename: "{app}\cowboys.mde"; IconFilename:
"{app}\cowboy.ico"
Name: "{userdesktop}\My Program"; FileName: "{app}\cowboys.mde";
IconFilename: "{app}\cowboy.ico"

The above creates a program dir, install my mde, and the icon file, and then
makes shortcut on the desktop..and also in the start->Programs menu.

The other advantage of inno install is that you get ONE "setup.exe" file (as
opposed to autorun.inf, and "files folder" and setup.exe). I mean, sure, if
you are deploying to a cd, then the autorun stuff is nice. However, if you
are just going to email, or provide a download page to update/install the
files, then a single .exe file is far better.

Since you are not actually installing the runtime, then in effect you are
just copying a few files to the users computer. I would consider using Inno,
as it is free. You can go and get the orca tools, and start messing around
with LARGE scripts...but as you can see, the above script is rather small,
and the inno setup includes several "sample" scripts that you can modify
(that is what I did with the above).


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal