You might want to take this concept just a little futher. I have done the same since FOW 6, but my UPDATED fact also contains the Description filed. This is where I put a short note on what changed during the last update. When sharing a database, updates made by others are noted by their use of initials in the Description field along with the description. Very handy for knowing what was modified by others for merging back into the "master" database. Dick > > Wayne League's answer to Charles Gohlke's problem works fine as long as the > database hasn't been entirely reconstructed, e.g. by making a GEDCOM, > deleting the database, and making a new one from the GEDCOM. I do this > occasionally after a batch of merges, and all the people in the > reconstructed database have the same Date Last Edited. I get round this by > making a new event "Updated", which records the date, the fact/event > altered, and which is preserved through a reconstruction. Also I don't have > to worry about whether I press "Cancel" rather than "OK", the latter > altering the Date Last Edited. > Colin Wilton-Davies in sunny Jersey, Channel Islands > > > > > _________________________________________________________________ > MSN 8 with e-mail virus protection service: 2 months FREE* > http://join.msn.com/?page=features/virus > > > ==== FAMILY-ORIGINS-USERS Mailing List ==== > The Genealogical Companion http://www.geocities.com/SiliconValley/2399/tgc.htm > Browsable Archives: http://archiver.rootsweb.com/th/index/family-origins-users/