Terry Reigel

You're welcome. Terry

You can identify them with the List of Citations report, which will show the person and tag where each citation occurs. To do that, use a "Filtered Group" with a filter like: Source No. = [?] When you run the report you will be asked for the specific source n;umber, which you can type in or look up with the Search (binoculars) button. If you use sureties, I'd suggest going to the report Options and unchecking Sureties on the General tag - that makes similar citations sort together better.

To amplify a bit on Les' comments, there are really two ways to do it. The most common is to have the [M] variable in the Sentence of the tag. Some default tags have that variable, but many do not. The other way is to specify in the report definition that Memos of tags without the [M] variable be printed anyway. This is generally not as satisfactory, as it gives you no control over where that contents of the memo appear. Also, it applies to all tags, even those you might not want to appear. I've added the memo variable, in conditionals to most of the standard tags: If you haven't found it by now, my article on sentences is here.

As I asked in your earlier post on the same subject, and to which you have not responded, in which of the name fields are you entering the Jr. and III?

You're welcome. Sometimes the words just don't connect. Terry

Have you done what Paul suggests above? If so, what happens?

In which of the name fields are you entering the Jr. and III? It should work correctly if you enter it in the Suffix field.

There is no such assumption built into the Roles in TMG - that is nothing tells the program that if one principal is assigned a specific Role, then the other princiapal should be assigned a different specific role. Rather, the second principal is assigned the Role following the first on the list of Roles. That's why you get the results you expect in the one case and not the other..."Bride" is listed first, with "Groom" following. So, if you assign Bride, the other principal gets Groom. But if you assign Groom, the other principal gets the next role in line, apparently Bridesmaid in your case.

When I try it, the person who I add is assigned the selected role, but the spouse is assigned the role of "Principal" - which is not supposed to be legal. I'll report it to the developers.

I don't see a way to identify name and relationship tags with a specific source cited in any report that can then set a flag. However, you could use a List of Citations report, with a filter like: Source No. = [?] When you run the report, you will be prompted for the source number, which you can then either type in or look up with the Search (binoculars) button. I recommend turning off the sureties option on the General tab of Options to better group the results. This report lists the tag type - look for name or relationship tags. This is still not an easy process, but is easier, I think, than going back to the book.

You're welcome. Terry

The repository reference field can be printed in source notes - with the [Repository Reference] element, which is not new. But, as you say, I don't think it's a particually good place for a presonal reference number. For one thing, to use it you would have to attach a repostitory to every source. There basically two ways to include a personal doc number. Which you should use depends on whether you have one doc number per source, or several. If you have only one, it's easiest to put it in the Source Definition. That's what Teresa's suggesting - create a custom source element in a little used group. At the bottom of my article on Source Elements & Groups is a listing of the least-used groups. If you assign multiple doc numbers to a TMG Source, you need to put the doc no. in each citation. The [CREF] source element and it's field on the Citation screen was created for just that use.

You're welcome, Dirk. Terry

What is the Sentence for your Census tag? Sounds like you have copied one that included the date directly in the Sentence, instead of getting it from the date entry.

1. When you create a report to screen, printer, or PDF file that has endnotes turned on, the note reference numbers are created in the report, and the endnotes are "accumulated." Then you run an Endnotes report to get the actual notes. The note numbers are continued if you run several reports, so you can run one set of endnotes for the group of reports. If you send the report to a word processor file, the footnote/endnote codes are included in the file, and then your word processor creates the actual notes from those codes. 2. No, the note reference numbers are assigned in the order in which they appear in the report, and are not related to the source numbers used in TMG.

You can change the backup destination under File > Preferences > Current Project Options > Adanced. By default it's the A:\ drive. Whether you can backup directly to a CD depends on the software you have installed to burn CDs - the "normal" Windows installation cannot do that. But in any case, I agree with Bob that the best plan is to backup to your hard drive, then occasionally copy that to a CD. In fact, I put a button on my custom toolbar to do a "one-click" backup to my hard drive. I use it whenever I feel I'd done more dat entry than I'd care to do over. It then gets backed up off the machine from there.

Tags cannot be printed individually. They are intended to be printed as part of a report about the person to whom the tag is attached. There is a preview narrative report on the Reporting toolbar that is useful for this purpose. (View > Toolbars to turn it on. Save the layout if you want it to be open next time you open TMG. You can also print all kinds of report from the Report menu, and can specify that only specific tag types be included if you like.

Trouble is, most users use letters, rather than numbers for there "related-by" flags. For example, I use: A = ancestor S = sibling of ancestor C = cousin M = spouse of any of the above P = parent of spouse So a "greater than" or "less than" feature would not be helpful to do what you are suggesting because the values were chosen to make them easy to remember, rather than for their sort order. However, users can already do exactly what you want, regardless of the flag settings they use, by creating a flag that marks those they want to include. Then use the List of People report to set that flag using any combination of one's "related-by" flag or any other characteristics that are useful.

As I recall, when you merge Data Sets, the custom flags in each one are kept, and the people who were not part of the DS in which the flag originally exited are assigned the default value of the flag. So, I'd suggest this method: 1. For each DS, create a custom flag. For example, for DS #1, create a flag "One", with values Y,N. This will set the value Y for everyone in the DS. Close Flag Manager and allow the flag to be set. 2. Open Flag manager, and change the values for the flag to N,Y. This makes N the default, but doesn't change those already set. Thus in the merge, the people from the other two DS's will have the flag set to N. 3. Do the same for the other two DS's - create a Flag "Two" and " Flag "Three." 4. Merge the three DSs into one. Now, in the merged DS, create a new flag with the three values you want to use. Say it's called "Source" and has values N,1,2,3, where N will be assigned for all people you add after the merge. Next, use the Secondary Output of the List of People report to set this new flag based on the three old ones. Use a Filtered Group, with a filter like: One = Y Then, on the Secondary Output tab of Options, tell it to set the new flag, Source, to 1. Run the report, and allow the flag to be set. Change the filter to the second old flag, and change the Secondary Output to set the Source flag to 2. Repeat for the third flag. Then delete the three flags that came from the three DS's. You could do something similiar by noting the ID#'s and filter on them, but this seems more foolproof.

You're welcome. Terry

First, as Lorna has already suggested, I'd urge you to look at my site, especially the Basic Data Entry Tutorial. Like all tags, you need to look at the sentence to be sure how the various fields are intended to be used. Apparently you are using the UK edition, since that tag type is standard only in that edition. It provides for several Roles, but since you didn't mention them, I assume you are using the default Principal role. The default Sentence for it is: [P]appeared in the 1891 census . From this, we can see that it's designed to have either one or two principals (the [P] and [PO] variables). It's designed to optionally have the place entered in the place fields (which would be called by the variable). Any other information you care to enter in the Memo would appear (because of the [M] variable), after a period, so that text should be entered with the first word capitalized. There is no [:CR:] code, so it's designed to flow with the other tags in the narrative, and not be in it's own paragraph. The output would then be something like: "He and Sally Smith appeared in the 1891 census of Lower Podunk. They were reported as owning their own home." (Can you tell I don't know a thing about UK censuses? ) Apparently you didn't take everything out of the Sentence, or you wouldn't get this text. Exactly what does the Sentence now say? It looks like it contains something like: [P] 1891 census Be careful to look at the sentence for the same person you are looking at in the report - there is a separate sentence for each principal. The larger issue with census is to figure out exactly what you want the census tag to record. Note that a census can be either a source or an event, or both, depending on your preferences. Most users would use it as a source for name, birth, parent-child relationships, etc., depending on exactly what information the particular census contains. Many users also create a census tag. But there is no agreement among users about exactly what should be recorded there. I prefer to record the "event" of enumeration - it gives an easy way to show in narratives where the family was, and who was in the household. My method is described in the census tag articles on my website. But other users prefer to record the exact record from the census, which some want to print in reports, and others prefer to use just as a repository of that information. These various applications require different Sentences, and different methods of data entry. That's because the 'She 1891 census' is not coming from the Memo, but from the Sentence. So putting the return in the Memo doesn't help. You would need to put it at the beginning of the Sentence. But first we need to get your sentence aligned with the way you want to use the Census tag.

Yes, I see it, and will report it to the developers. Thanks.

There are several aricles on my website (link below) that might help - especially those in the "Basics" section, the Basic Data and Source tutorials, and the one on Importing.

See my "Related-by" article for some ideas on how to do this.

To place marriages, or any tags for that matter, in a desired order when the actual dates are not known, enter a Sort Date that places it in the proper place relative to the other tags. Sort dates are only available in Advanced data entry mode. To switch modes, go to Preferences > Program Options > Data Entry.