[AccessD] Runtimes - Preferably AccessXP but 2003ifabsolutelyrequired

That is doable. After the installation file is run on each machine then the
FE can be replaced whenever needed. This can be done via pretty much any
method. I send out updates - usually zipped but sometimes installation
routines that are pretty much just an automated unzip. you could have an
automated routine that checks for a new version on the server and downloads
it before starting the app. (That's where I'm headed.)

As to the Word mail merge I would suggest late binding rather than
referencing so that the version of Word doesn't matter. I use it for mail
merges and the speed isn't an issue.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Monday, January 29, 2007 9:37 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Runtimes - Preferably AccessXP but
2003ifabsolutelyrequired

Thanks John.  I have a "best offer" out on Ebay for an OfficeXP developers
edition.  If I get it I will worry about the rest.

One issue with this application is that it is pretty much constantly under
development.  So I need to install a runtime, but then do the "download the
FE from the server every morning" routine.  The biggest issue I see is that
the application does word automation for mail merge so I guess that some
fixed version of word has to be installed on each user machine so that I can
reference and manipulate that.

John W. Colby
Colby Consulting
www.ColbyConsulting.com