The distribution I mentioned was an Access 2.0 client application,
conditional installation of Access 2.0 itsself, and conditional installation
of third-party image processing software. This distribution was, initially,
sent to the new user on CD, and later in the life of the project, downloaded
by the user from a central server. The Wise Installer script determined the
need to install Access and the third-party software. There were no tables on
the remote user's machine, except some rarely-changed lookup tables in the
Access client database (U.S. States and Canadian Province postal codes, for
example).
If you are using only the Packaging Wizard in the Developer Edition or the
Visual Studio Tools for Office 2003, then I believe you _may_ need to create
multiple setups. It has been some time since I created an install with the
Microsoft tools, and that was just for a demonstration.
In most of my client work, full retail Office Pro was on the desktop of each
user because the client companies knew that information workers could make
good use of database software, in addition to the "developed applications"
we were providing. In those shops, there was no "install" -- just copy the
Access database(s) from a server folder to the user's folder.
Larry Linson
Microsoft Access MVP
"Salad" <hiddenvalley@ranch.com> wrote in message
news:3FE10B12.7A0D41D6@ranch.com...[color=blue]
> Both you and Scott brought up a topic that I have a question on.
>
> Let's say I distribute a new version. Folks with a prior version already[/color]
have[color=blue]
> 1) the database back end and 2) the run-time files. Do you create 3[/color]
setups...1[color=blue]
> for the database backend the second for the front end and the third for[/color]
the[color=blue]
> runtime?
>
>
> Larry Linson wrote:
>[color=green]
> > Yes, Wise and SageKey get high marks but they are not cheap stuff. I[/color][/color]
worked[color=blue][color=green]
> > on a project where I assisted in choosing Installer Software, back in[/color][/color]
1995,[color=blue][color=green]
> > and I found only one significant difference, web installation, and that[/color][/color]
was[color=blue][color=green]
> > the deciding factor for the prime contractor. I think, though, by the[/color][/color]
time[color=blue][color=green]
> > we actually distributed anything, InstallShield had the feature, too.
> >
> > One of my colleagues did the scripting and found it very powerful. We[/color][/color]
did[color=blue][color=green]
> > not use SageKey partly because we were not distributing runtime -- the
> > client company had thousands of unused Access 2.0 licenses and were
> > installing full retail Access 2.0, along with the Access 2.0 client
> > application, and a third-party graphics/imaging package.
> >
> > Larry Linson
> > Microsoft Access MVP
> >
> > "Scott McDaniel" <scott@NOSPAM__thedatabaseplace.net> wrote in message
> > news:9c6dnTDJqrh00n2iRVn-gw@comcast.com...[color=darkred]
> > > I just packaged a runtime dist with a smallish db (around 6 megs, no[/color][/color][/color]
data[color=blue][color=green]
> > in[color=darkred]
> > > the tables). I use the Wise Professional version 9.0 with sagekey[/color][/color][/color]
scripts.[color=blue][color=green][color=darkred]
> > > The package includes all the files necessary to upgrade, if necessary,[/color][/color][/color]
the[color=blue][color=green][color=darkred]
> > > target machine (MDAC 2.7) and a few references (Total Access memo, an
> > > Activex Email control) and the standard other items.
> > >
> > > The download was 47 megs. Quite a download for any user, especially[/color][/color][/color]
one on[color=blue][color=green]
> > a[color=darkred]
> > > dialup ... I doubt they would even take the time to do it. The Wise[/color][/color][/color]
system[color=blue][color=green][color=darkred]
> > > offers an intelligent updater option that I am exploring to see if I[/color][/color][/color]
can[color=blue][color=green][color=darkred]
> > > distribute only the front end and have it automatically be installed[/color]
> > (after[color=darkred]
> > > the customer does a full install, of course), and I'm fairly sure it[/color][/color][/color]
will[color=blue][color=green][color=darkred]
> > > work OR include my necessary files (the frontend, basically) and store[/color]
> > other[color=darkred]
> > > files (like the runtime, MDAC installs, etc) on my secure server and[/color][/color][/color]
have[color=blue][color=green][color=darkred]
> > > the install program download and install as needed. I believe the Pro
> > > version can do this, but I'm still researching it. At almost $1000 US[/color]
> > (plus[color=darkred]
> > > $425 for the Sagekey scripts) you better have a real need for it.
> > > --
> > > Scott McDaniel
> > > CS Computer Software
> > >
www.thedatabaseplace.net
> > >
> > > "MLH" <CRCI@NorthState.net> wrote in message
> > > news:um1vtvobao8h7c99dkcdjfcmbsufbh748u@4ax.com...
> > > > I have little or no knowledge as to how a runtime Access database
> > > > application might be distributed from a website. I am sure that I'm
> > > > about to find out. I do have one question for you wizards though...
> > > >
> > > > My experience has shown that when I have installed applications
> > > > from the web, my browser generally asks what I want to do with
> > > > the file... Do I wanna save it? or Do I wanna run it? The browser
> > > > generally warns about the dangers of executing downloadable
> > > > files. My typical procedure is to save the file to a known location
> > > > and run it offline - or at least after closing running[/color][/color][/color]
applications.[color=blue][color=green][color=darkred]
> > > >
> > > > Is it possible to offer only the alternative of running the install
> > > > executable and prohibit downloading?
> > >
> > >[/color][/color]
>[/color]
