Quite some time ago, I got some assistance from Dennis Kowallek (creator of LTools) because I used SEARCH and REPLACE in an attempt to get rid of a SOURCE event globally, not realizing the correct way to do so. Anyway, he helped me with coding to correct the problem.
Now I notice that apparently the apparent bug is not fixed because SEARCH and REPLACE allowed me to delete an EVENT NAME and replace it with a blank (null character, I guess). Probably a dumb thing to do, but I was working with a backup and wanted to see what would happen. What happens is that all the EVENT NAMES get blanked out, but can no longer be accessed through SEARCH because the EVENT NAME no longer exists. However, the detail under that EVENT NAME does exist and shows up when you look at the individual records. I would think this could be considered a bug in that Legacy should never allow a person to do this. How do I report this bug which might work this way on several things, namely SOURCES and EVENTS? Thanks, Jerry Boor - Michigan PS--I just re-joined the Legacy users' lists, so if you reply to this message, would you also CC me initially to make sure I'm getting the messages back? Thanks. 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
