Thanks for that - at least I know it's not just me. Human error would be too easy a solution!
As the problem is occurring in just one field that, as far as I can see cannot be separately printed, it's particularly worrying as I don't know the extent of the data loss. Legacy Technical have now suggested a Search/Find/Create List but, unfortunately, the method that was suggested was not possible within Legacy, so I am awaiting further contact from them. Paul --- On Wed, 13/10/10, Jan Roberts <[email protected]> wrote: > It has certainly been experienced by > at least one other (me) some time ago - but seemed to > resolve itself and has not re-occurred(Touch wood!) > - source detail was being replaced with random - often > single - characters. And no, nothing to do with Source > Writer as I always use basic sources. > > -----Original Message----- > From: Connie Sheets [mailto:[email protected]] > > In > other words, the only way I can replicate your problem is to > make a human error. > > I'm not saying that's what happened to you, but as you > probably know, intermittent problems that only a handful of > users experience are the hardest to identify a cause and > fix. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
