duplicate fields in my name when preparing reports

[ddcolby]

When looking at my family card, all appears well. When I try to prepare a report such a family group sheet, under my name is birth, birth, birth, baptism, baptism, baptism. The information on the first birth/baptism is correct; the second and third set is incorrect. How do I get rid of the second and third set?

Thank you.

[David G. Kanter]

When looking at my family card, all appears well. When I try to prepare a report such a family group sheet, under my name is birth, birth, birth, baptism, baptism, baptism. The information on the first birth/baptism is correct; the second and third set is incorrect. How do I get rid of the second and third set?While you haven't cited which specific version of Reunion you are using, I'll respond based on Reunion 8.06

That suggests you have multiple occurrences of those Events in your record. (The View for the Family Card will only show the first of any such same-named multiple occurrences.)

Open your record (click on your name to get to the Edit Person window) and select the Events tab. I'd expect you'll find multiple Birth and multiple Baptism entries. If so, select each superfluous entry and click the Delete Event button.

There's an easy way to find all the records which contain more than one occurrence of any Event, Fact, or Note. Do Find->Anything and set the Condition to <# of Duplicated Fields> <More Than> <0>. (You'll find the "# of Duplicated Fields" in the "Attributes" entry of the pop-up menu.) You'd want to run that for the People and then again for the Couples tabs in the Find Anything window.

In my case, when I find a need (or expect to have a need) multiple occurrences of something (e.g., Immigration where the person went from their birth country to another country and, then from there to 3rd country, etc.), I define a series of the applicable fields (e.g., Immigration #1, Immigration #2, etc.) so even if I have no date (in the case of an Event), I can explicitly record the order in which the activity occurred. (In the case of Emigration & Immigration, I've created 5 sets of those fields as that seemed to be sufficient to cover the "worst case".) As Reunion makes it easy--as a 1-time operation--to create whatever fields you might want and there's no significant overhead with having extra, currently-used fields, I've found that the best way for me. As they say: "Your mileage may vary."