On 2010/05/03 14:28, [email protected] wrote: > If it's a problem for Legacy users, then it's on topic, particularly > if there's a possible easy fix. MD5 is heavy artillery and would > require Legacy to perform significant calculations - once when a file > is first used as Legacy media, then for every such file when mass > actions like export or archiving occur. Unless things have changed > since I last messed with file systems, all files terminate with a > checksum. Using that should be simple, fast and compact. Odds are > very low that a filename and file checksum would not be unique within > one user's machine.
<LAZY USER MODE ON> If you scan an image and use the defaults, you'll end up with something like scan1.jpg. Move that file to folder A. Scan another, different image, and you'll end up with scan1.jpg again. That scuppers your odds! <LAZY USER MODE OFF> Also... show me where the checksum is in a text file :-) -- Regards, Mike Fry Johannesburg Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
