Terry Reigel

I see the same issue when testing. It appears you cannot copy a person from a locked Data Set by selecting them in the Project Explorer. However there it works fine if you put the person to be copied in the Focus Group, then use that for the copy. I suggest you use that method. I don't know whether this is intended or not, but I'll report it to the developers.

To expand on Vera's reply, Parent/Child relationship tags do not print in most reports. Instead, the primary parent/child tags are used to create the parent/child relationships that the report depicts, depending on the type of report or chart you are using. Non-primary parent/child tags are simply ignored. If you want non-primary relationships, such as God Parents, to appear, it's best to enter them as events, rather than as relationship tags. God Parents, for example, can be entered as witnesses on a baptism tag, with a suitable sentence. They will then appear in the narratives of both the child and the God Parents, or either, as you choose.

You can limit your search to a single tag type like this if you know what type of tag you used, or omit the first line and search all tag types. Note that the search is literal - it looks for exactly what you enter, so if your search text is different by a single letter, even a space, it will not be found. Thus it's best to search for just a key word or phrase that you are sure you used.

Great! You're welcome.

This means that you have a citation to Source #0 - which shouldn't happen, since there is no source #0. The trick here will be to find that citation and either remove it or change it to the correct source number. The source notes after the name are 1) the citations for the name tag, 2) the citations for the parent/child relationship tag that connects this person to his or her father, and 3) the citations for the parent/child relationship tag that connects this person to his or her mother. That is, provided those citations are turned on on the Sources tab of report Options. They are on my default. The fact that you only have two notes suggests that either there is only one parent identified for this person, or that one of the tags has no citation. To find the problem, double click on each of the three tags at the top of the Details window - the ones labeled "Name" "Father" and "Mother." In each tag, look at the citations. Two of those tags should have a citation to source #0. Remove or fix that citation, and all should be well.

You're welcome. Yes - it's fine to use to restore your settings on the same machine, but when you move to a different drive/folder structure (as you could moving to a new computer) it's best not to restore this part. Yes. Sorry, I meant to address that in my previous response. The restore wizard works through all the items you are telling it to restore, asking you to confirm those in question, then it actaully does the restore of those items you end up telling it to use. So after you say "No" to some items, there will be other items, like the project itself, that it still has to restore. I think what's happening here is that many file types, like layouts and filters, have some default files that are generated during installation or initial use. If you backup includes these, you are asked if you want to overwrite the existing ones. In that case it really doesn't matter which you answer - the restored defaults will be the same as the existing ones. The real purpose of these confirmations is when you restore over a copy you have been using. In that case, the layouts, report defs, filters, etc. that you have created are likely to exist both on your installation and in the restore, though perhaps with different versions. So you are asked whether you want to keep the current version or restore the old one. In the case like you had, when you are restoring previous settings to a new installation, I think so. If you were restoring over a working copy and had some later changes in the current files that you don't want to overwrite, you couldn't.

That would be the problem. Since you said you were using the default sentences, I thought they might have been imported, and I think that only happens from UFT projects. Looks like "somebody" had worked on this sentence.

The restore of projects and customizations includes quite a few different types of files, which listed with the check boxes at Step 3 of the restore wizard. You can restore any or all of them independently, so if you said "no" to some items they didn't get restored, such as layouts or report configurations. As long as you don't find something important missing, no big loss. If you do, you can run the restore again, and check only that item at step 3. The item that was warned about possible incompatiblities is the Program Options in Preferences. The problem is when you move to a new machine, or even a new HD, the logical drives and folders may be different, causing problems with some settings. It's safer to reset these options manually than to restore them on a machine with a different setup than the one on which the backup was made. I don't think you have any problems other than a few of your custom settings may not have been restored.

More people do add more entires on the Picklist, etc. But unless your computer is very old and feeble, at those numbers you shouldn't have any problems with the system handling it. (I have 15,000+ in my main database.) Should to explore custom tag types, source types, and the like, it's much easier to manage if everyone is together. That's a very good idea - I find it helps a lot. Use the Expanded Picklist if you aren't already, as it displays Accents. Also, use flags to control the Accents as you suggest, rather than the filters like "is a descendant of..." - system response is much faster. If you have any questions on setting them up, you might look at my Accents article. You're welcome.

The only time I've seen this is when the copied text includes a line break before the actual desired text.

That doesn't look like it's from the default sentence, which is: [P] [M] Note that there is no "a" in the default sentence, and there are no conditional brackets, so you should get "and unknown value" if there were no entry in the memo field or a surety setting problem. You didn't import this data from UFT by any chance? I suggest you check the sentence and make sure it includes the [M] variable.

You're welcome, Brooke.

You're welcome. Sorry, but a single link is one more than is allowed. The whole idea behind multiple data sets in a project is that they are absolutely, positively, independent. Thus you cannot link in any way people in different data sets. That means that you could not, for example, create an ancestry report for you which would include both branches. If that doesn't matter to you, then go ahead and keep them in separate data sets. Otherwise, I would copy the new line into your existing data set. I'm still now sure what your reservation is about doing that - if you could articulate that, perhaps we could offer a suggestion that might help.

You're welcome, Dave. Terry

You're welcome, Les. Terry

Yes, more or less. First, you only need to add to supress the tag memo it you use one of the option in the report definition to print memos that are not in the sentence. As long as you choose "none" on the Memo tab of report Options, it doesn't matter what you put in the sentence - no extra memos will appear. While I've not found a use for the Memo options, so users do find them useful. Thus, I recommend assuming you will find a use for it later if not currently, and constructing your sentences accordingly. If you use the Memo options, you do need to include in witness sentences when you don't want the main tag memo to appear. The witness memo is treated entirely separately, so th presence of [WM] does not supress the main memo. I've tested this in TMG reports, but not in SS, so can't be entirely sure they work the same. But since it's required in TMG reports, I go ahead and include it.

Lorna's explaination is right on. For a fuller discussion, with "pictures," see my article on Merging Projects and Data Sets.

If the "reference tag" only exists for those want to removed it from, I believe John Cardinal's TMG Utility can do that. Check it out here.

So far as I know, the only way is to add sort dates to those tags. Sort dates ar only available in Advanced data entry mode - go to Preferences > Program options > Data Entry to change to that mode.

I'm totally confused about what you want to do. You don't want to put the data in your existing Muddock data set, but you want to then merge them? What's the difference? I'm with Mike - I think a single data set is almost always best. Keeping separate ones often requires duplicate entery, prevents outputing in common reports, and create serious overhead if you create custom tag types, source types, styles, etc. If we understood more clearly what you want to accomplish, I think we could offer some specific suggestions.

Well, yes, if I could figure out what the question is. Well, sort of. You can always use [W] in the sentence for a witness to refer to that witness. It doesn't matter whether that witness is assigned a role other than the default Witness role or not. Similarly, you can use [P] in the sentence for a principal to refer to that principal, whether or not you have assigned a non-default role to that principal. In fact, I highly recommend that practice - see the "Defining Role Sentences" section of my roles tutorial. In some constructs, such as my method of dealing with "first," "second," and "third" marriages, it's much easier than using the role variables.

I disagree that any data needs to become "real" if the user understands what it is and why it's entered. Like John, I enter married names as finding aids. I never include then in any reports that I send to anyone, nor in data I publish on the web. I suspect you would be even further dismayed with another finding aid I use - the creation of "Standard Names." For my lines which have changed the spelling of the surname over the years, I choose a "standard" spelling (generally the most current one) and create a name tag with that spelling for everyone who used a different spelling. In this case I'm quite sure that the people never used that spelling, but I do so because it makes it easy for me to find ancestors who used various spellings without having to recall in which generation the spelling changed. Again, those names are never included in output. Likewise I enter all sorts of speculation, theories, and other notes that may well not be true, but I identify it and where appropriate, source it, so it's nature is clear should I choose to include it in output. You are of course free to adopt any style of use that serves your needs. I've posted replies here only so readers will see that there are alternate styles of use that are at least as valid.

Actually, study of family history in the past few centuries is full of such instances. For example, I'm looking at cemetery records, and find Mary Fenker. It's a good chance that that's a married name. But if I didn't have married names in my data, I'd have to look through 15,000 people, find all the Marys (also Marias, Anna Marias, etc.) and try to find one that married a Fenker. Or, I could just look for Mary Fenker, and see if one matched. Or, I'm looking at a record of Ann Cobb, needing to post more surety as adminstrator of her husbind's estate. I could look through several hundred Anns, Mary Anns, etc., for one that married a Cobb. Or, I could just look for Ann Cobb if I've entered married names. Why would you click on a woman who's married name was Ann Smith if you were looking for women who were born Ann Smith? There's the primary marker right there to tell you whether you are looking at the primary name or an alternate name, like a married name. If you doubt, as you say, the husband's name is right there to tell you it's a married name you are looking at.

As long as you haven't customized the sentences locally (within the individual tag) you can add to each Role in the Tag Type Definition. Older tags with no entry in the Witness Memo will be uneffected. Or am I misunderstanding your question?

Do not use GEDCOM - lots of your TMG data may be lost, and what's preserved may not be in the same format as you entered it. Use the Backup and Restore process instead. Create a backup on your old computer. Then copy it to your new computer. The easiest way is by use of a local network between the two computers, if you have one. If not, you can copy it to a floppy disk, if it fits, or burn it to a CD, then read the disk in the new computer.