[AccessD] Front End Updater

I'm using a external .ini file, along with the access project custom 
property of "build" date ie, 20050512.1 I download the .ini and check it 
locally, if the version in the ini is newer than the properties then I 
download the new copy and launch my .exe setup and close out my access 
program.

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
> 
> >
> >
> 
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.11.9 - Release Date: 5/12/2005
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



-- 
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...