On 11/30/2012 3:34 PM, Ed Leafe wrote:
On Nov 30, 2012, at 2:32 PM, "MB Software Solutions, LLC"
<[email protected]> wrote:
Seems like a hash of some sort would be the way to go versus filetostr() but perhaps
not. OTOH, why not just compare the file's datetime stamp? If difference found
though, I could just copy the file down (again). For the large files, I control them
with timestamp fields, so I guess for those I would simply say "grab everything
beyond the MAX(LocalDBF) key value...since these records are just added to the pile
and not edited.
Hmmm...it's good to talk it out here! ;-)
If you want to know if the contents have changed, hashing is the way to
go. If you want to check if it has been accessed, then the timestamps might be
better, although those can be manipulated. Do you care if a file was changed
and then reverted?
Hi Ed,
The network file is just a source repository of records that only get
added to as time goes on. There are never any edits...just new records
added. Also, "reverting" should never happen in this instance. ("Never
say never!")
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
http://fabmate.com
http://twitter.com/mbabcock16
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
