If it's a new child, then you also have to send the pages for the parents, else there is no link to the new person. Similarly, if it's a newly found parent, then you have to send the pages for each child. The idea is fine in theory, but if you have added or updated 100 or so people it's very difficult to work out which files to upload - ends up quicker reloading the whole lot "to be sure".
So a "dynamic" feature based on a database would be far simpler and could presumably be tailored to include more/less data to suit our differing wants. Jack -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Steve Hallberg Sent: 30 January 2005 14:09 To: [email protected] Subject: Re: [LegacyUG] Dynamic Data Retrieval > On 1/30/2005 5:23:53 AM (Pacific time), you wrote: > If it's a new person, then > it's a new page in sequential number order and can easily be found. This is not necessarily true; if 're-use abandoned RINs' is set in the program's options, the new page will most likely not* fall in sequential order. -------------- Steve Hallberg Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
