[AccessD] One Accdr (front end) for each User's PC or Share theAccdr file on the File Server

Ha!  Kid stuff!   :-)

Early this year, I wrote one which checked the current version of Tables, Data and Forms 
recorded in a system table and then looked on Dropbox for update files, all of which had a 
version number as part of the filename.

A table update file consisted of  lines of SQL Drop, Create, Alter, Add statements to run on 
the BE tables

A data update file consisted of lines of  SQL Insert, Update statements to run on the BE 
tables

There could be multiple Table or Data update files in the repository which had to be run 
sequentially.

A forms update file was a  replacement FE accdb with the version number appended to the 
filename which was copied down and renamed if newer.  

Once the updates were done, a log file (and a separate error log file if necessary)  were 
uploaded to Dropbox.

THEN  the application was opened.

(All done with a few hundred lines of PowerBASIC code)


-- 
Stuart

On 22 Oct 2014 at 10:08, David McAfee wrote:

> I did something similar at my last place with ADP FEs using VB.Net and
> also in C#.
> 
> The exe would look at a .ini text file and read the top line to get
> the latest version
> 
> I numbered the FE's (MachineTracking 433.adp) , if the number after
> the "MachineTacking" didn't exist in the user's directory, I'd copy it
> over and launch it. If it did exist, I'd just launch it.
> 
> I'd delete the last group of files if they existed (MachineTacking
> 42*.adp), rather than the previous in case someone was on vacation or
> out for a while.
> 
> David
> 
>