[AccessD] Automatic Update Function

My first consideration would be to check that the app has properly closed, and
has actually finished tidy-up work processing before the download starts.

Then, there is also the problem with ensuring the download has actually
completed, and all the files registered, and any views, or extracted data
entries cleared out before the app is restarted, and the restart locks the user
out until the base data environment is setup.

Then - why would you need to close the app - a more usual process is for the app
to be started from a batch process that would check a keyset (in a flat .txt
type file ) on the client machine matches the current one on the server/storage
location, and if different, then redo the download of the entire front-end.
Yes - that may take a while but the alternative is to have to be very sure that
all the bits of the new version are included in the download.

Then - there is checking that the client system is actually a full match for the
sourcing system - and the other systems.

-----------------------------
I am currently having to ship just 1 client of a group a 2003 version of an app
that runs under 2007/2010 on all environments.
That 1 client system reports the shipped 2010 file needs repairing and then,
after 'repairing the 2010 download fails.
If I convert the app to a 2003 file, and ship that - the client can upgrade it
back to 2010 and all works!

And .. all the client systems are maintained by a central support site - so
should (Ha!) have the same setup!  

JimB 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erbach
Sent: Friday, February 27, 2015 2:45 PM
To: Database Advisors
Subject: [AccessD] Automatic Update Function

Hello all -

Do any of you have a favorite approach/module that you use to automatically
update the front end on the user's machine?  My monster application from
WIFI hell has had auto update issues as well as corruption issues.

My co-worker that developed part of the app with me wrote an auto update
module that

Creates a batch file on the fly
Closes Access
Runs the batch file to copy the new front end to the user's machine and
then re-opens access

At least that's what's supposed to happen...there have been a number of
times that I've been suspicious about whether or not this auto update is
somehow triggering back-end corruption too, although I don't know why it
would.  There have been many times when the app is up and running fine on
10 machines and when the 11th machine starts up and goes into auto-update
mode the whole thing comes crashing down.  Maybe that's just coincidence.

BTW, I'm implementing the 'write to CSV' option today to try and stop the
corruption...

Janet Erbach
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com