StuJol said:
ok, this sounds good. I will give it a try. Can i put both installs onto 1
disk or should i have 2 seperate disks. If both are on one disk how do i
run
the install for both of them?
You simply create two directories...and put in each install. Of course, this
means the disk will not auto install. So, even better would be to use
inno...and wrap both part 1, and part 2 into a single install process......
The following inno script would install the runtime
[Files]
Source: "*"; DestDir: "{app}"
Source: "files\*"; DestDir: "{app}\files"
Source: "files\setup\*"; DestDir: "{app}\files\setup"
[Run]
FileName: {app}\setup.exe; Parameters: "/qb"
note we are just simply useing the "setup" command with a /qb (q = quiet, b
= progress bar). The "q" thus eliminates all of the prompts (and questions
like custom/typical install). This is the msi (Microsoft) setup we are
talking about here.
You have to play with inno for a few hours..but it really is easy to learn
and use. Read the help..and there is also a newsgroup for inno (you find all
of this in the link I gave you).
Further, since you are likely not a 100% perfect developer, you going to
need
to setup a "update" disk (or better web site) where people can
download/install a updated version of your software (and, you will NOT need
to re-install or even waste space packaging the runtime anyway....they
already have it!!). So, having a separate install prepares you a whole
setup systems that will allow easy update of your uses (and, you will have
to do this anyway...so, might as well kill two birds with one stone).
IF you look at the following ms-access screens...you can see that I use a
web site..and inno installer to update my software...
http://www.kallal.ca/ridestutorial/upgrade.html
The last few screens are not ms-access...but of course inno....
The intial help screens etc..are ms-access....
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal