[AccessD] Front End Updater

Elam, Debbie DElam at jenkens.com
Thu May 12 14:02:19 CDT 2005


What about Ted Avery's Front end updater?  I use that one quite a lot.  John
Colby has it on his site under Useful Files.

Debbie

-----Original Message-----
From: Arthur Fuller [mailto:artful at rogers.com] 
Sent: Thursday, May 12, 2005 1:52 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Front End Updater


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
- JENKENS & GILCHRIST E-MAIL NOTICE - This transmission may be: (1) subject
to the Attorney-Client Privilege, (2) an attorney work product, or (3)
strictly confidential. If you are not the intended recipient of this
message, you may not disclose, print, copy or disseminate this information.
If you have received this in error, please reply and notify the sender
(only) and delete the message. Unauthorized interception of this e-mail is a
violation of federal criminal law. 
This communication does not reflect an intention by the sender or the
sender's client or principal to conduct a transaction or make any agreement
by electronic means.  Nothing contained in this message or in any attachment
shall satisfy the requirements for a writing, and nothing contained herein
shall constitute a contract or electronic signature under the Electronic
Signatures in Global and National Commerce Act, any version of the Uniform
Electronic Transactions Act or any other statute governing electronic
transactions.



More information about the AccessD mailing list