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.
kb Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
