[AccessD] Access 2007 Runtime

The old packaging wizard from earlier allowed for not including the
runtime, but then the user was required to have a full version of Access
or the runtime already installed.  The advantage to using scripts is
that they give you much finer control over the installation and where it
goes and how it behaves.  It used to be quite painful to create desktop
icons with the packaging wizard or to allow the user to determine where
the front end and back end should be installed on *their* system.  With
scripts and Access 2002 and later, you can set up the whole runtime app
the way you want it or the way the users wants it without impacting the
existing versions of Access and without affecting any other runtime
version installed.

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Schapel
Sent: Tuesday, June 26, 2007 12:15 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Access 2007 Runtime

Charlotte,

The Package Wizard in the Access 2007 Developer Extensions provides for
including the Runtime, but also provides the option to not include the
Runtime, and prompt the user to download and install the Runtime at
installation.

I am assuming that the advantage with Sagekey installation script
continues to be the handling of potential conflicts with already
installed prior versions of Access.

Regards
Steve


Charlotte Foust wrote:
> You still need to package your app with the runtime, Rocky.  You just 
> don't have to buy VSTO to do it for Access 2007.
> 
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com