Arthur Fuller
artful at rogers.com
Thu May 12 13:52:04 CDT 2005
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