[AccessD] Front End Updater

Arthur,

I use a version updater I found through Access D some years ago
written by some fellow in Chile, I believe. It looks at a version
number in a local table on the user's w/s and compares it to the
version number of the most recent version on the LAN. If the LAN's
version is higher then it's downloaded. The download location is the
same on every user's w/s. I found someone to help me translate the
Spanish messages and have been using it ever since.

Steve Erbach

On 5/12/05, Arthur Fuller <artful at rogers.com> wrote:
> I know that this has been kicked around several times in the past, but
> I'd like to know the current thinking on this subject. Given N users on
> a LAN (and it might be a WAN), we want to place any updates in one
> standard place (probably using a hardcoded reference to the box and dir)
> and then have a mechanism that checks to see if the update is more
> recent than the version locally loaded.
> 
> What puzzles me about this is: given Access's habit of re-timestamping
> the ADP/MDB file upon loading, how do you compare versions to see which
> is more recent? A laptop user, for example, currently disconnected but
> going to be connected tomorrow morning, may have a more recent timestamp
> on her file than the one on the net. How do you get around this problem?
> 
> TIA,
> Arthur