Re: [LegacyUG] Potential Problem Report

Thanks so much for this detailed information. Douglas On Sun, 17 Jul 2022 at 15:16, Cathy Pinner wrote: > Douglas, > PP = Potential Problem - the subject of this thread. > > Tag is a way to group people in Legacy. There are 9 tags. You can see > the tag boxes on Family View if you turn them on a

Re: [LegacyUG] Potential Problem Report

Douglas, PP = Potential Problem - the subject of this thread. Tag is a way to group people in Legacy. There are 9 tags. You can see the tag boxes on Family View if you turn them on at Options > Customise 1.5 There are also Hashtags in Legacy 9 as 9 tags were never enough. I now use Hashtags fo

Re: [LegacyUG] Potential Problem Report

Hi Cathy, Excuse my ignorance, but what is a tag and also PP. Doug On Sat, 16 Jul 2022 at 16:56, Cathy Pinner wrote: > Yes Ian, > Look at each tab and you'll find you can tag people with a PP. > You may want to adjust the criteria and so tag only people with the same > issue. > Once checked, you

Re: [LegacyUG] Potential Problem Report

Yes Ian, Look at each tab and you'll find you can tag people with a PP. You may want to adjust the criteria and so tag only people with the same issue. Once checked, you can also mark as not a problem but beware those with mother older than 50 - the child may be the child of an unmarried daughte

[LegacyUG] Potential Problem Report

Potential Problems Report (under Tools) I have found a large number of records with a problem, some as obvious as "Birth Date after Death Date." = my typos, but many are "Birth Date after Mother is 50 years old." - which I believe have correct dates and persons (parents/children). Is there a m

Re: [LegacyUG] Potential Problem Notification

My father and his first wife had a child born six months after my sister! She was born very preterm but she lived for some hours and it didn't bother Legacy at all. On November 23, 2017, at 12:13 PM, Roberta Montpetit wrote: One of my mother's cousins had a single child in December,  then twi

Re: [LegacyUG] Potential Problem Notification

Don't forget gestation is closer to ten months than nine☺ On November 23, 2017, at 8:46 AM, Debbie Medeiros wrote: Good morning,  I have a question about birth dates and potential problem notification coming up. "Child 2 born too soon after prev child" Child 1 is born Feb 8, 1929 and Chil

Re: [LegacyUG] Potential Problem Notification

One of my mother's cousins had a single child in December, then twins less than 8 months later. That would really confuse the system! 😀 On Thu, Nov 23, 2017 at 10:37 AM, Debbie Medeiros wrote: > Thank you everyone for the help. I never would have thought to look under > the tools tab. > > Hap

Re: [LegacyUG] Potential Problem Notification

Thank you everyone for the help. I never would have thought to look under the tools tab. Happy Thanksgiving! Debbie On Thu, Nov 23, 2017 at 8:54 AM, Brian Kelly wrote: > To answer your first question there is less than 12 months between Feb 8 > 1929 and 17 Jan 1930 and the default gap check for

Re: [LegacyUG] Potential Problem Notification

To answer your first question there is less than 12 months between Feb 8 1929 and 17 Jan 1930 and the default gap check for births too close together uses 12 months as the criteria. Those number boxes to the right of each gap can be used to change the number of months. You can highlight and ty

Re: [LegacyUG] Potential Problem Notification

ytree.com <http://www.legacyfamilytree.com/> From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Debbie Medeiros Sent: Thursday, November 23, 2017 8:46 AM To: LegacyUserGroup@legacyusers.com Subject: [LegacyUG] Potential Problem Notification Good

Re: [LegacyUG] Potential Problem Notification

I am forever getting this "error". Sometimes it is because there are births I've yet to discover and haven't yet filled in all the gaps, but quite often it doesn't seem to understand that there CAN be more than a year between each child! It is annoying, but my advice is, unless they change this not

[LegacyUG] Potential Problem Notification

Good morning, I have a question about birth dates and potential problem notification coming up. "Child 2 born too soon after prev child" Child 1 is born Feb 8, 1929 and Child 2 is born Jan 17, 1930. Why is Legacy telling me that the amount of time between these two children's birth is shorter th

RE: [LegacyUG] Potential Problem with dates

: legacyusergroup@LegacyUsers.com Subject: RE: [LegacyUG] Potential Problem with dates Ron, . You could also try exporting your records into a new Legacy family file: Click on File > Export > Export to a new Legacy Family File. Give your new family file a name and click Save and the Legacy

Re: [LegacyUG] Potential Problem with dates

On 2015/07/18 06:15 AM, Jim Terry/Support wrote: > I am sorry for the joke. We don't always get it right in tech support, > especially when we have just a sentence or two worth of problem description > and don't have the family file to examine and test. What about a progressive search for the off

RE: [LegacyUG] Potential Problem with dates

e prompts. . If all else fails, restore your family file from your backup copy. Jim Legacy Family Tree Technical Support Original Message > From: "Goodwin Genealogy" > Sent: Friday, July 17, 2015 7:54 PM > To: legacyusergroup@LegacyUsers.com > Subject:

re: [LegacyUG] Potential Problem with dates

--- > From: "Adrian Purkiss" > Sent: Friday, July 17, 2015 8:05 PM > To: legacyusergroup@LegacyUsers.com > Subject: re: [LegacyUG] Potential Problem with dates > > Jim > > Sorry not intending to bash you personally rather support in general. No point in suggesting s

re: [LegacyUG] Potential Problem with dates

Adrian Sent from my android device. -Original Message- From: Adrian Purkiss To: legacyusergroup@LegacyUsers.com Cc: remotes...@wavp.co.uk Sent: Sat, 18 Jul 2015 4:03 AM Subject: re: [LegacyUG] Potential Problem with dates Jim Sorry not intending to bash you personally rather support in

re: [LegacyUG] Potential Problem with dates

clear as Ron doesn't say what problem is being reported. More details are required. Regards Adrian Sent from my android device. -Original Message- From: Jim Terry/Support To: legacyusergroup@LegacyUsers.com Sent: Fri, 17 Jul 2015 11:26 PM Subject: re: [LegacyUG] Potential Problem

RE: [LegacyUG] Potential Problem with dates

10 To: legacyusergroup@LegacyUsers.com Subject: re: [LegacyUG] Potential Problem with dates Ron, Sometimes i have had a record for a person that has unusual problems like you are reporting. I have fixed the problem with check and repair. See http://support.legacyfamilytree.com/article/AA-00749 fo

re: [LegacyUG] Potential Problem with dates

Jim Not intend Sent from my android device. -Original Message- From: Jim Terry/Support To: legacyusergroup@LegacyUsers.com Sent: Fri, 17 Jul 2015 11:26 PM Subject: re: [LegacyUG] Potential Problem with dates Adrian, You forgot to bash me for my 2nd suggestion! Jim Legacy Family Tree

re: [LegacyUG] Potential Problem with dates

Adrian, You forgot to bash me for my 2nd suggestion! Jim Legacy Family Tree Technical Support Original Message > From: "Adrian Purkiss" > Sent: Friday, July 17, 2015 1:30 PM > To: legacyusergroup@LegacyUsers.com > Subject: re: [LegacyUG] Potential Prob

re: [LegacyUG] Potential Problem with dates

Sent: Fri, 17 Jul 2015 9:10 PM Subject: re: [LegacyUG] Potential Problem with dates Ron, Sometimes i have had a record for a person that has unusual problems like you are reporting. I have fixed the problem with check and repair. See http://support.legacyfamilytree.com/article/AA-00749 for the steps

re: [LegacyUG] Potential Problem with dates

To: legacyusergroup@LegacyUsers.com > Subject: [LegacyUG] Potential Problem with dates > > I am experiencing a problem with the Potential Problem reports, for some > reason it is not reading the entered dates properly. > > > > It is reporting a problem where it says that the e

[LegacyUG] Potential Problem with dates

I am experiencing a problem with the Potential Problem reports, for some reason it is not reading the entered dates properly. It is reporting a problem where it says that the entered date is 1774 where the date that I have entered is 1874. I have run the "check/repair" several times and have de

Re: [LegacyUG] Potential Problem Checker

ample, I’ve > seen 1 month old infants listed that I know were actually born just past the > official cut-off date and therefore should not have been listed. This is all > part of what makes genealogy fun. > > Brian in CA > ------------ > > >

RE: [LegacyUG] Potential Problem Checker

-- From: Leon Chapman [mailto:chap...@gmail.com] Sent: Wednesday, December 10, 2014 1:17 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Potential Problem Checker Brian: I created a new event called "Tombstone" which I use frequently with an attache

Re: [LegacyUG] Potential Problem Checker

and Facts after death date) > > Bottom line: It's not really a major problem and doesn't affect report > generation. I can continue to ignore these types of problems. Hopefully some > future update will take a look as why the exclusion setting is not working or > maybe mak

RE: [LegacyUG] Potential Problem Checker

not working or maybe make sure Census Events are hard coded to be excluded. Brian in CA -Original Message- From: Brian/Support [mailto:br...@legacyfamilytree.com] Sent: Tuesday, December 09, 2014 2:43 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Potential Problem Chec

RE: [LegacyUG] Potential Problem Checker

n/Support [mailto:br...@legacyfamilytree.com] Sent: Tuesday, December 09, 2014 2:43 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Potential Problem Checker Some events are hard coded so they will not generate a potential problem as an event after death because they always occur after

RE: [LegacyUG] Potential Problem Checker

Marvelous! CE > From: br...@legacyfamilytree.com > To: legacyusergroup@LegacyUsers.com > Subject: Re: [LegacyUG] Potential Problem Checker > Date: Tue, 9 Dec 2014 17:42:32 -0500 > > Some events are hard coded so they will not generate a potential problem > as an event aft

Re: [LegacyUG] Potential Problem Checker

Some events are hard coded so they will not generate a potential problem as an event after death because they always occur after the death date. The programmers did some work in the last little while on those. The obituary is one of those that may now be in the hard coded not a problem list. Brian

RE: [LegacyUG] Potential Problem Checker

ail.com] Sent: Tuesday, December 09, 2014 10:54 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Potential Problem Checker Some people would call that a problem that has been fixed. To others it's a new problem. -- Richard Van Wasshnova On Tue, Dec 9, 2014 at 9:06 AM, Ke

Re: [LegacyUG] Potential Problem Checker

Some people would call that a problem that has been fixed. To others it's a new problem. -- Richard Van Wasshnova On Tue, Dec 9, 2014 at 9:06 AM, Kelly Booth wrote: > I just installed the latest update 2 days ago. This morning, I added 3 new > obituaries and noticed that the icon that comes up

[LegacyUG] Potential Problem Checker

I just installed the latest update 2 days ago. This morning, I added 3 new obituaries and noticed that the icon that comes up when you put in a date after the death was not there. I double checked my dates to verify the obit dates were after the death dates and I did not have them marked to be

Re: [LegacyUG] Potential Problem

Thanks Brian, It is on the Individual Edit Screen List of Events. Now I know it is a known problem I will leave it until the next update. Many thanks for the help. Marion On 23 June 2014 23:13, Brian/Support wrote: > There is a known problem where the PP Indicator does not disappear from > the

Re: [LegacyUG] Potential Problem

There is a known problem where the PP Indicator does not disappear from the Individual Edit Screen List of Events when it is marked as Not a Problem. This has been fixed and will be included in the next update to Legacy 8. If your problem does not relate to the Individual Edit screen event list th

Re: [LegacyUG] Potential Problem

Hi Mike, Comes up with "Event Date is out of range" and the usual Click to View Details etc etc. I had right clicked on all of them (the five) and ticked Problem/Event fact before/after Death but the icon still appears. I thought it would have gone as I had said it was not a problem in these instan

Re: [LegacyUG] Potential Problem

On 23 Jun 2014 14:51, marion wimsett wrote: > Thanks Mike, I had ticked that event as not a problem but the icon still > remained so I wondered if there was another item that I had missed. > I had made a detailed report on each child about being included in the Census > despite the fact they had d

Re: [LegacyUG] Potential Problem

Thanks Mike, I had ticked that event as not a problem but the icon still remained so I wondered if there was another item that I had missed. I had made a detailed report on each child about being included in the Census despite the fact they had deceased before the due date but have left the Census

Re: [LegacyUG] Potential Problem

On 23 Jun 2014 14:14, marion wimsett wrote: > I have a family with 11 children, which I have traced through the Censuses > to 1911. I had three of them as being dead before the 1911 Census so I double > checked the entry on the 1911 Census. > For some unknown reason the householder (the father)

[LegacyUG] Potential Problem

Little bit of guidance please. I have a family with 11 children, which I have traced through the Censuses to 1911. I had three of them as being dead before the 1911 Census so I double checked the entry on the 1911 Census. For some unknown reason the householder (the father) had listed all 11 childr

Re: [LegacyUG] "Potential Problem" button

The easiest way to exclude someone from a PP alert is to left click the alert and then choose Mark as not a Problem. If you right click, you then have to find the right category to tick. The Mark as Not a Problem button does that for you. Cathy Brian/Support wrote: > > Hover your mouse on the red

Re: [LegacyUG] "Potential Problem" button

Hover your mouse on the red problem button and instructions will pop up. One of those is right click to exclude the problem. That will open the person's exclude from potential problems screen. If you have difficulty or questions at any stage press F1 or use the help button on the screen for more i

Re: [LegacyUG] "Potential Problem" button

On 03 May 2014 06:21, John Schneider wrote: > In Legacy 8 there is a "Potential Problem" button to alert us of problems. > I > have several of these alerts which are incorrect and I can't find how to > correct > the alert button. Many of the medieval persons don't have surnames and the > war

[LegacyUG] "Potential Problem" button

In Legacy 8 there is a "Potential Problem" button to alert us of problems. I have several of these alerts which are incorrect and I can't find how to correct the alert button. Many of the medieval persons don't have surnames and the warning states that the surname is in all upper case, when in f

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

Subject: Re: [LegacyUG] Potential Problem - Unrecognized Event Date On 25/04/2014 04:09, Cathy Pinner wrote: > However, I think there is a bug in that you don't seem to be able to > override the problem checking for this particular event OR override > the date checking for the individ

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

On 25/04/2014 04:09, Cathy Pinner wrote: > However, I think there is a bug in that you don't seem to be able to > override the problem checking for this particular event OR override > the date checking for the individual. > > Jenny, have you been able to exclude a problem like this? Yes and no! I

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

Paula, I don't think there is a viable alternative for this sort of date. Nothing else makes English sense. I guess if you really can't stand the PP alert, you can put the date in the notes and write a sentence override for this event. However, I think there is a bug in that you don't seem to be

RE: [LegacyUG] Potential Problem - Unrecognized Event Date

Legacy would recognize “to 1977” … C.G. Ouimet Kingston ON From: Paula Ryburn [mailto:paula.ryb...@sbcglobal.net] Sent: April 24, 2014 11:13 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Potential Problem - Unrecognized Event Date I have one event where I want to say

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

On 24/04/2014 16:12, Paula Ryburn wrote: > So, what would be your recommendation on "until 1977" ... "through > 1977" has same result. Just enter what I want and ignore the PP? > Because I apparently cannot tell Legacy to ignore the PP, because > nothing happens when I click on it in the Event sc

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

(not intended to I think). Thanks,   --Paula From: Ward Walker To: legacyusergroup@LegacyUsers.com Sent: Monday, April 21, 2014 3:23 PM Subject: Re: [LegacyUG] Potential Problem - Unrecognized Event Date I try to word everything so that it makes sense both now and at any point in t

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

On 21/04/2014 23:40, Jay 1FamilyTree wrote: > Actually, After 1980 would be recognized by more genealogy software > programs if imported from a gedcom rather than from > Maybe so, but "After 1980" means something entirely different to "From 1980". -- Jenny M Benson Legacy User Group guidel

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

l 21, 2014 3:40 PM > *To:* legacyusergroup@LegacyUsers.com > *Subject:* [LegacyUG] Potential Problem - Unrecognized Event Date > > In trying to clean up my Potential Problems, my sister has an > unrecognized event date. I am trying to say that she worked at her present > posit

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

the correct recognized date is “From 1980” From: Howlanddavisii Sent: Monday, April 21, 2014 3:40 PM To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Potential Problem - Unrecognized Event Date In trying to clean up my Potential Problems, my sister has an unrecognized event date. I

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

Ward: Thanks for the suggestion; it has resolved the problem. Now to look for others and do something similar. Howland Davis -Original Message- From: Ward Walker To: legacyusergroup Sent: Mon, Apr 21, 2014 4:24 pm Subject: Re: [LegacyUG] Potential Problem - Unrecognized Event

Re: [LegacyUG] Potential Problem - Unrecognized Event Date

date field. In notes, you can say things like ‘she started in 1980 and was still in that position as of Apr 2014’. Ward From: Howlanddavisii Sent: Monday, April 21, 2014 3:40 PM To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Potential Problem - Unrecognized Event Date In trying

[LegacyUG] Potential Problem - Unrecognized Event Date

In trying to clean up my Potential Problems, my sister has an unrecognized event date. I am trying to say that she worked at her present position from "1980 - present." If I want to say that, how do I do so? Should I not have spaces around the dash (similar to actual dates), do I leave

Re: [LegacyUG] Potential Problem Report - Illegal Characters

HTML before using it in Legacy.  Ila Johnson From: MikeFry To: legacyusergroup@LegacyUsers.com Sent: Wednesday, January 29, 2014 2:42 PM Subject: Re: [LegacyUG] Potential Problem Report - Illegal Characters On 30 Jan 2014 00:38, Dave Naylor wrote: > On

Re: [LegacyUG] Potential Problem Report - Illegal Characters

Thanks  I'll add "and" between the two surname variations.   I do like the Potential Problem report, but have had to "change" a few of my ways of entry.   Personally I like to immediately view the variations rather than use the aka. Ron, hope you're doing well. Syble On Wednesday, January 29

RE: [LegacyUG] Potential Problem Report - Illegal Characters

You are the only person in the group that does NOT need to see an optometrist. J Brian in CA Yeah, I didn’t see it either. From: Dee Ziegler [mailto:dee.zieg...@gmail.com] Sent: Wednesday, January 29, 2014 3:06 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Potential

Re: [LegacyUG] Potential Problem Report - Illegal Characters

In the illegal characters I see \/ -- backward slash, forward slash -- though the combination looks very much like a capital V (the letter). Dee in Maryland On Wed, Jan 29, 2014 at 5:55 PM, Larry Lee wrote: > It appears to me that she has the forward slash "/" not the vertical bar > "|". >

Re: [LegacyUG] Potential Problem Report - Illegal Characters

It appears to me that she has the forward slash "/" not the vertical bar "|". What would happen if you put the second name in ( ) s? I don't see them in the forbidden character list. Larry Lee Sent from my Nook On Jan 29, 2014 3:43 PM, "MikeFry" wrote: > On 30 Jan 2014 00:38, Dave Naylor wrote:

RE: [LegacyUG] Potential Problem Report - Illegal Characters

Syble, I have Hayes and Heyes and use the AKA. It is the only way which I know that is suitable and problem free. Additionally one can also search on that field. Ron Ferguson http://www.fergys.co.uk/ Syble Glasscock wrote: ># 6714, I have surname as Coffee/Cofey > #6706, I have Hays/Hayes >

Re: [LegacyUG] Potential Problem Report - Illegal Characters

No spam warning on this message. Congratulations! On Wed, Jan 29, 2014 at 5:42 PM, MikeFry wrote: > On 30 Jan 2014 00:38, Dave Naylor wrote: > > On 29 Jan 2014 Syble Glasscock wrote: > > >> #6706, I have Hays/Hayes > > > >> I received this: > > > >> [6706]The following characters are not usu

Re: [LegacyUG] Potential Problem Report - Illegal Characters

On 30 Jan 2014 00:38, Dave Naylor wrote: > On 29 Jan 2014 Syble Glasscock wrote: >> #6706, I have Hays/Hayes > >> I received this: > >> [6706]The following characters are not usually found in a name: > !@#$%^&*_ +=|\/;:><~` []{} 0123456789. ^ | What's thi

Re: [LegacyUG] Potential Problem Report - Illegal Characters

On 29 Jan 2014 Syble Glasscock wrote: >  #6706, I have Hays/Hayes > I received this:  > [6706]The following characters are not usually found in a name: !@#$%^&*_ +=|\/;:><~` []{} 0123456789. > Remove any erroneous characters. But you do not have any of those characters in your surname field s

[LegacyUG] Potential Problem Report - Illegal Characters

# 6714, I have surname as Coffee/Cofey  #6706, I have Hays/Hayes Is there a way to have the two spellings rather than in the aka I received this:  [6714]The following characters are not usually found in a name: !@#$%^&*_ +=|\/;:><~` []{} 0123456789. Remove any erroneous characters. [6706] The fo

Re: [LegacyUG] Potential Problem display for an individual

On 20 Jan 2014 02:36, Tony Rolfe wrote: > I have a person flagged with a potential problem, "Birth too long after > prev child". There is a red button next to their birth details and when > I hover over that, the pop-up says "click to view details". So, I click > and a reasonably big window appe

[LegacyUG] Potential Problem display for an individual

My "Edit Children" button is greyed out, so I'm guessing it applies to the children of this person, not to her siblings. I went back out of the edit individual screen to the Pedigree View window (where 7.5 had a useful display of her siblings) and did the right-click and view siblings shuffle. No

Re: [LegacyUG] Potential Problem display for an individual

yes, it will. You need to click on the Edit Children button > > > On 20 January 2014 10:36, Tony Rolfe > wrote: > > I have a person flagged with a potential problem, "Birth too long > after > prev child". There is a red button next to their birth det

Re: [LegacyUG] Potential Problem display for an individual

click on the actual red dot - that will bring up a box where you can tell it to ignore the problem if it's something that needs to be ignored On 20 January 2014 10:36, Tony Rolfe wrote: > I have a person flagged with a potential problem, "Birth too long after > prev child". There is a red butt

[LegacyUG] Potential Problem display for an individual

I have a person flagged with a potential problem, "Birth too long after prev child". There is a red button next to their birth details and when I hover over that, the pop-up says "click to view details". So, I click and a reasonably big window appears with a single line "Child 9 born too long aft

[LegacyUG] Potential problem with shared events

While merging duplicate Individuals recently one, RIN 30749 had an 1854 baptism which the other did not. I merged 30749 into the other, copying baptism and it's source resulting in 30749 being deleted. A few days later a File Maintenance resulted in: There are 3 Individual Vital Event record(s) t

Re: [LegacyUG] Potential Problem - Birth too soon after marriage

ox is checked. > > > > Regards, > > Tom > > > > *From:* Mary Young [mailto:m...@cmy.org.uk] > *Sent:* 05 January 2014 21:38 > *To:* LegacyUserGroup@LegacyUsers.com > *Subject:* [LegacyUG] Potential Problem - Birth too soon after marriage > > > > I&#x

RE: [LegacyUG] Potential Problem - Birth too soon after marriage

oup@LegacyUsers.com Subject: [LegacyUG] Potential Problem - Birth too soon after marriage I'm using Legacy 8 Deluxe v.8.0.0.367, and enjoying all the new features, including the red markers for Potential Problems. "Birth too soon after marriage" is a useful addition - but I can't find it

[LegacyUG] Potential Problem - Birth too soon after marriage

I'm using Legacy 8 Deluxe v.8.0.0.367, and enjoying all the new features, including the red markers for Potential Problems. "Birth too soon after marriage" is a useful addition - but I can't find it in the "Exclude from Potential Problems" list. Can someone help me? Thanks Mary Young Legacy Us

RE: [LegacyUG] Potential Problem

: LegacyUserGroup@LegacyUsers.com Subject: [LegacyUG] Potential Problem I have an individual that has a 'Note' event where the date is before the birth date. This shows up as a 'Potential Problem' in the 'Individual's Information' window. When I mouseover, Legacy

[LegacyUG] Potential Problem

I have an individual that has a 'Note' event where the date is before the birth date. This shows up as a 'Potential Problem' in the 'Individual's Information' window. When I mouseover, Legacy reports "event date out of range" I right click and go to Problems tab and tick the entry for 'Ev

Re: [LegacyUG] potential problem alerts

ons -> Customize -> 3.3 set to Initial Caps -> Apply > > This will change all your surnames to the initial caps standard. > > *From:*Rebecca Williams [mailto:rebecca.w...@gmail.com] > *Sent:* Monday, December 16, 2013 6:24 PM > *To:* LegacyUserGroup@LegacyUsers.com > *

RE: [LegacyUG] potential problem alerts

Options -> Customize -> 3.3 set to Initial Caps -> Apply This will change all your surnames to the initial caps standard. From: Rebecca Williams [mailto:rebecca.w...@gmail.com] Sent: Monday, December 16, 2013 6:24 PM To: LegacyUserGroup@LegacyUsers.com Subject: [LegacyUG] potentia

Re: [LegacyUG] potential problem alerts

Go to Search>Replace> Surname Find SURNAME check box Match Case Replace Surname Start On Mon, Dec 16, 2013 at 4:23 PM, Rebecca Williams wrote: > This was a minor problem with earlier versions, but now the problem alert > is in my face and I want get rid of it. > When I entered most of my p

Re: [LegacyUG] potential problem alerts

Have you tried shift + right click on the problem alert icon. Click Standardization (tab), uncheck "Surname entered as all uppercase", then click Close. I'm sorry if this has already been suggested or if you have done this and it is not solving your problem. On Mon, Dec 16, 2013 at 7:23 PM, Rebe

[LegacyUG] potential problem alerts

This was a minor problem with earlier versions, but now the problem alert is in my face and I want get rid of it. When I entered most of my people, I used All Caps. How do I get rid of the error. I really don't want to go to each and every person and check the box that it is not a problem. How do

Re: [LegacyUG] Potential Problem (date) won't correct

Kathy and Bryan, et al, First, An obit event should always be after death so in the event definition, the event should have Exclude from Problems checked so it never is a problem. If yours is not checked, check it. Second, sometimes the alerts are tricky as to what is the problem. When you see t

Re: [LegacyUG] Potential Problem (date) won't correct

have you moved away from that person's screen and then come back? I have noticed as much as a 5 second delay in the (!) leaving after an item is checked as ok. second option would be run a check and repair third option would be to exit and reload if none of those fix it, then come back with some

[LegacyUG] Potential Problem (date) won't correct

W8.1 32bit, Legacy 8.0.0.356 An individual’s window shows a generic problem (!). His information screen shows a (!) next to an Obituary event which, of course, is after the death or burial event. Clicking the event gives a checkbox (at the very bottom) “Exclude this instance of this event from

Re: [LegacyUG] Potential Problem List

On 2010/06/08 22:39, Jenny M Benson wrote: > Tim Rosenlof wrote >> While in the Potential Problems Dialog, what is the difference between >> 'Create Problems List' and 'View Existing Problems List' ? They seem to >> produce the same output for me, with the options to print, save, . >> . What am

Re: [LegacyUG] Potential Problem List

Tim Rosenlof wrote >While in the Potential Problems Dialog, what is the difference between >'Create Problems List' and 'View Existing Problems List' ? They seem to >produce the same output for me, with the options to print, save, . >. What am I missing ? The former causes Legacy to go off and

Re: [LegacyUG] Potential Problem List

Tim, Create builds the problem list and lets you view it. View just re-opens the existing problem list and then lets you view it. Ron Taylor Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com

[LegacyUG] Potential Problem List

Hi yall, While in the Potential Problems Dialog, what is the difference between 'Create Problems List' and 'View Existing Problems List' ? They seem to produce the same output for me, with the options to print, save, . . What am I missing ? Regards, Tim Rosenlof Legacy User Group guideline