Terry Reigel

After you re-install as Paul described, you unlock with your existing code. You must enter the same e-mail address that you used when you got that code, as they are linked. But, that e-mail only shows in the Help > About screen, so it's not really a big deal. If you want your e-mail to appear in the "prepared by" section of reports, enter you current e-mail in Preferences > Current Project Options > General.

Yes, there clearly is - things don't happen by accident. The problem is, whatever that mechanism is, it was not designed for the purpose of sorting tags. I'd guess it was designed for the purpose of efficient processing of data, or something of that sort. Thus, there is no assurance that the tags you find in the "right" order today will be in the same order tomorrow, for the simple reason that tag order was never part of that design. Routine data entry and maintenance is likely to upset the order you currently see. The only function designed to control sort order, and thus can be depended upon to do that consistently, is the sort date.

Most people don't enter them as undated, entering either the official "as of" date or the actually enumeration date if known. If you add a sort date they should be moved to their proper sequesence with respect to all other dated tags. Do you see something different? There is an option to but all undated tags at either the top or bottom. Within the list of undated tags, the order is unpredictable. I suspect it has something to do with their order in the files, but I've observed that editing an undated tag can cause it to move. I don't believe there is any reliable way to control sorting other than with the tool provided for that purpose - sort dates.

Good question. I don't see a way to do it.

You can limit the report to BMD tags by going to the Tags tab in Options, and specifying "Selected" tags. Then, in the list that appears, select only the tag types you want included. If you want to replicate the one entry per line format, you can do that too but it's a bit more complicated. Probably the easiest way is to make a copy of your Project (File > Copy Project, but you have to close the Project before you can copy it). Then, in the copy, edit the Sentence in the Master Tag Type List of the three tag types you will use to something like: Birth: [:CR:]b. Marriage: [:CR:]m. [PO], Death: [:CR:]d. Then run the report from that project.

You're welcome - glad that finally nailed down. I've replicated the wrong number issue and will report it. My guess it's displaying an "internal" number and not the one users see. The difference I'd think is missing sources, or deleted sources, or something of the kind.

Lorna, Did you look at source #1063 - Peter & Jill Billing email "EM METTERS, Devon: ex P & J Billing"...? On the Attachments tab of the source definition, in the lower half "Sources of this Souce," you should see a citation to source # 2019 - Bere Ferrers: BAP Just delete that citation.

Jim is exactly right - you have this source cited as the "Source of this Source" in Source #1063.

In my view using Focus Groups to keep track of the separate lines is the hard way. Instead, I'd suggest using one or more custom Flags. Advantages: - You can put the Flag(s) on the Add Person screen, so it's easy to put new people you add in the correct group. - The flag can be used for Accents so you can color-code the lines in the displays. (Using the Focus Group for Accents is both much more limited and slower). - You can use the flag directly to control websites made with Second Site, and indirectly to control Exports to other types of websites and reports.

Tricky doesn't even begin to describe it. Never, ever, use export and re-import to split a data set! All sorts of custom tag types, source types, styles, and more is lost. All custom sentences are lost. The sources will be a mess. Instead, use the Secondary Output of the List of People to create new Data Sets or Projects. This keeps all the details intact. I do agree, generally, with Mike's points about keeping everyone in a single Project if possible - among the issues if you don't is the difficulty of keeping custom tag types, source types, and the like the same in each separate project.

I can't replicate anything like it - looks like a tag type with no name, appearing for person #1063, who has no name. I suspect some sort of data corruption. I think a chat with support would be the next step.

You can separate it with the List of People (LoP) report, using the Secondary Output (under Options on the report definition screen) to create a new Project. This will copy everyone in the LoP to a new Project. Do this once for each of the three new Projects you want. Each will contain all the information about the people included in it, as well as the custom tag types, source types, styles, etc. that you have created. The trick, however is to get the right people in each of the three lists of people, so the right people end up in each new project. It's easy if you only had direct ancestors in each of the three lines. But more likely you have also siblings of ancestors, some of their descendants, their spouses, parents of spouses, and more. With a complex array like this, you cannot use a single filter in the LoP to specify them. You have two choices - 1) collect each group in a Focus Group, or 2) create a temporary flag or flags, and use the LoP to set the flag(s) to mark who is to be sent to each new project. With as large a project as you have, I'd recommend the flag method, as it's easier to keep track of who's included, and whether anyone is not included in any group. To do that, open Flag Manager (File menu) and create one or perhaps three flags. You could create one flag with 4 values - ?, A, B, C - if everyone will be sent to only one Project. But I suspect that a few key people will go in several projects, so I'd suggest three flags, each with values of N, Y. Once the flag is created, use the LoP report's Secondary Output and filters to set the flags correctly for all the people. Since I'm assuming you have a complex set of relationships included, some by blood and some by marriage, what you need to do is start with a key person, then repeatedly add ancestors, descendants, and spouses until you have found every one linked to a particular line, marking them all with the flag as you go. As you do that, you need to keep the process from going up the "other" trees and including them. The easiest way to do that is to determine where you want to "break" the trees apart, and temporarily make the parent child tags at that point non-primary. For example, say you are doing your line, and want to cut off you son-in-law's line after his parents. Go to each of those parents, and make their father and mother relationship tags non-primary (select the tag and press the * key). Do that for each line you want to cut off. Now, start the process of marking a line. Open the LoP, go to Options, and set the Secondary Output to change the flag for this line to Y (you might what to check the box on that screen to suppress primary output, otherwise you will have to wait for the list to be created at each of the many steps). Now create a filter like: Is an Ancestor of ID# 123 (where 123 is any starting person in this line) At the bottom, under "Then Add" check spouses, ancestors, and decendants for as many generations as appear in your data. Run the report, and allow the program to change the flag. You've now added the ancestors of your starting person and all their descendants. Next we start to collect other linked people. Back to the LoP, and change the filter to: YOURFLAG = Y and leave the "then add" terms as they were. Run the report, and on the Filter Progress screen, note how many people are added in the terms at the bottom of the list. Repeat this process until no new people are being added. Each time you run it, you probe farther into the links by marriage, their ancestors and descendants, etc. How may passes are required depends on how complex your data set is. When no more people are being added, do the same with each of the other two lines. You may need to change where you put the non-primary parent child links if you want some people to be duplicated in each new project. This process picks up everyone who is somehow linked by blood or marriage. If you have non-linked people - some entered only as witnesses, or some not linked at all, you need to decide where they go. I'd suggest this approach: In the LoP, create a filter like: YOURFLAG1 = N AND YOURFLAG2 = N AND YOURFLAG3 = N END with all the "then add" terms unchecked. This list will be everyone not now included in one of the sets. You could set the flag for them manually to put them in the desired group, or if you want them all in one group, use the Secondary Output to do that. Now, with the flags set, you are ready to actually create the new project. This time, set the Secondary Output of the LoP to create a new Project. Use a filter like: YOURFLAG = Y (choosing the correct flag) with the "then add" terms all unchecked. Run the report and allow the new project to be created. If any parts are unclear, please ask for help.

I think what you are doing is a fine way to handle the issue - I do much the same. Add parts to standard tags where it makes sense, then but the rest in Memos of one or more tags. The advantage of using a custom tag type rather than the standard Anecdote tag is then it's easy to exclude them for a particular report, should you care to later. I typically break up such narratives into several tags, so I can position other tags between when it makes sense. Also, I put parts that I can verify with other sources into separate tags so I can show multiple sources for those parts.

You're right, Virginia. I'm now seeing it on those pages as well. I didn't think I did when it first appeared. Terry

It only appears on the pages for individual topics, like this one, and not on the pages listing all the topics. Could that be the issue?

You're welcome.

You are on the right track. Use the Focus Group to define who you want to copy to a new project. Then, use the List of People report to copy everyone in the Focus Group to a new Project. To do that, in Options in the List of People, go to the Secondary Output tab and tell it to create a new project. As to collecting the desired people in the Focus Group... The "Add Others" function applies to whoever is currently selected in the FG. So, enter the starting person of the branch, select them, and add Ancestors. Then, click the Select All button, then add Descendants. This adds all the cousins. Then, Select All again, and add spouses to include the spouses of the cousins. Now it gets a bit tricky. You probably have some parents of those spouses you want to add. So, Select All again to add Ancestors, But, you need to be careful to not select yourself, your children, or others whose ancestors would bring in the other branch of the family. Do that by either removing them from the FG, or by using Ctrl-click to unselect them before adding Ancestors again. To double check, you might want to set Accents to mark with color everyone who is in the FG, and navigate around the Project to see who is included. Once you are sure you have the right people, proceed to create a new Project with the List of People report.

Yes, there is. Open the Master Source List (Tools menu), select the desired source, and click the Cite Globally button.

The primary relationship tags, which are what your -Bio tags are, do not print directly in narrative reports. Rather, they are used by the reports to show parent/child relationships, details depending on how the particular report displays these relationships. That's why you can't add a sentence structure to Relationship tags. Since there are no relationships included in Individual narratives, the Relationship tags are not used at all in that report. Some alternatives: 1. Use a different type of report that does include them, such as Family Group Sheet or Journal. 2. Add the parents as Witnesses in the children's birth tags, with an appropriate sentence. The difficulty with this is that the statement will also appear in other report types, such as the Journal, where they are redundant.

I'm afraid it's not altogether simple to remove just specific people. The easiest way is to reduce the number of generations in the report so they aren't included. But, that may also eliminate some non-living people that you want to include. The way to exclude exactly those you want is to make a temporary data set that doesn't include those you want to omit, and make the report from that data set. One way to do that is: 1. Use the Focus Group to select those you want to include in the report (doesn't matter if you include extras, just be sure you don't include those you want left out. 2. Use the List of People report to create a temporary data set. Tell it to include those in the Focus Group, then, in Options, on the Secondary Output screen, tell it to make a new Project or Data Set containing only those people in the list (i.e., those in the Focus Group). Now, run the Descendant Narrative from that Data Set or Project.

In my view, one should either include details on living people, or don't print anything on them (there are people with strong views on either side of this issue). I see no point in including some names and not others (use of the "mother's maiden name" as a security word is foolish - there are many sources for this information available from potential mal-doers). If you really want to protect the living, simply exclude them entirely from the report. But, if you still want to include the names of living people, but exclude this one person, there is a simple way. Send the report to a word processor, then edit out the offending information before printing the report.

Sounds like you want a list of all people born on that day. So I'd use a List of People report, with a filter like: * Birth... Date Is exactly 12 Oct 1941

If it helps, TMG's "rules" putting source elements into GEDCOM output are described in my article on the subject.

Welcome, Cheryl! The default source templates are designed to use only the Citation Detail field on the Citation screen. The Citation Memo and Reference field are optional fields, to be used as the user prefers. If your preference is for the data you enter in them to appear in the footnotes, you need to modify the output templates of the sources to include the in the notes, in the position you like. The source element for the reference field is [CREF]. You can edit output templates for specific sources only, or for the source type, which will then be used for all sources of that type (provided they haven't previously been edited individually. See my article on Working with Source Templates for details.

You're welcome. Terry