Lee, Think of it this way...
When you click on a data field in Legacy to make a change, Legacy doesn't really "know" whats there, it just knows to "save" whatever you put there. even if you dont change anything, Legacy is still re-saving that data to that field. It wouldnt really know that that data was the same from the original. So your recording log would show many data fields that actually didnt have any change, but that you touched/ entered. Additionally, what if you went in and out 4 or 5 times getting a place name just right, each one would be stored as a change, your report would be FULL of thousands of lines of the tiniest of changes and many with no real changes at all. In some cases it may check to see if the data is in a specific format or check for some other detail, but I dont think it's storing original data anywhere. (other than in the sense that it doesnt overwrite the field until you click to the next field, so if you were in a field and started to type, but the used the ESC key to back out the original data is still in the field) At least that is my understanding of how Access Database code works, maybe a Legacy programmer can explain better. Jay On Thu, Jul 25, 2013 at 9:50 AM, Lee Bruch <lbr...@nwlink.com> wrote: > In access could you not create a field that records the date of each > change for every record, which would then be searchable by date ranges? > > > -----Original Message----- > > From: Mike Fry [mailto:emjay...@gmail.com] > > Sent: Thursday, July 25, 2013 12:21 AM > > To: LegacyUserGroup@LegacyUsers.com > > Subject: Re: [LegacyUG] Log of Changes > > > > On 2013/07/25 03:01, Brian/Support wrote: > > > > > There is no separate log file. Legacy only records the date changed > > > for individual and marriage records. You can search of people whose > > > individual or marriage change date is on a certain date, after a date > > > or before a date using Search > Find > Detailed Search. > > > > To accomplish what the OP asked, you first need a database that > > produces a journal. This is a file that when applied to a previous > > backup, allows you to come forward in time towards when the current > > file lost its' integrity. I don't think Access possesses such an > > animal. > > > > -- > > Regards, > > Mike Fry > > Johannesburg (g) > > > > > > > > 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/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > 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/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
