Wouldn't it be more effective to look up the actual date of Quasi in the effective year and enter that date? Many calculations will depend on a date and will not calculate a word.
Nevertheless, I agree that if one accepts the resulting loss of functionality, one should be able to mark "not a problem" and have the problem report thereafter go away. > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Monday, May 19, 2014 4:11 PM > To: [email protected] > Subject: Re: [LegacyUG] confirmation dates and error checking > > Thank you, ALL!! As stated before, the problem is with the error > checking, not the use of Quasi., etc. While I appreciate all the > attempts at helping, the answers given do not address the issue. > > If I "Mark as Not an Error" the error checking of that item should be > ignored. It still appears on the Family View. I would like it to > disappear from at least the family view so I don't have to check the > problem over and over again. I thought that was the purpose of marking > it as not an error. > What am I missing? > > Elsie > > <snip> 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 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
