Jim Byram

Sorry. I wasn't distinguishing name vs. abbreviation. I'll write up the issue.

Sigh! Numeric entry as Earl requested will be possible in v7 to allow entry of French department codes. No, you can't enter '-' as you found and I believe this is by design. These codes are used for web lookup using the place info and place maps options. It appears that the correct code for "Nouveau-Brunswick" is NB and not N-B. It could be that preventing characters such as '-' is to prevent users from making entries that would not work.

Neil, You are running TMG v6.12 as administrator? TMG uses it's own PDF printer driver. I just tested and found that it was necessary to permanently install the PDF printer driver using File / Printer Setup before I could output a report to PDF. Jim

More precisely... To easily do this, select the TAG by clicking the tag name in the TYPE column, then use CTRL-P (control key and letter P) to move to the person of interest. Works beautifully and is a very clever solution to the problem of navigating when the Tag Box item tips are enabled.

Please read the TMG 'Renumber People' help topic. 'Renumber People' has absolutely nothing to do with making the person ID numbers correspond to an alphabetical arrangement of all individuals in the database (although you could do this manually person-by-person which would be very laborious and would work fine until the next time that you added a person to your database). You need to start a new topic titled 'Second Site 2-Controlling the sort of exhibits on a website' or take that issue to the SS mail list which is a more appropriate place to ask the question.

Some people grouse about the media limitations of TMG but one program can't do everything. TMG does not have the image management abilities of iMatch and the acquisition/editing abilities of PhotoShop or almost all other third party applications. And it never will. Exhibit management/acquisition/editing will always be done better outside of TMG. v7 will have some subtle changes in the Exhibit Log that make what you must do from the EL easier.

That's not correct. All tables in a project are not updated simultaneously each time that a project is edited. If both versions of a project are edited and two-way synchronization is done, you could end up with a mix of tables from two versions of the project. The tables do not stand alone and have many links between each other. Such a synchronization would effectively disrupt the links between the tables and destroy the project. As you said, as long as you always backup both projects before any synchronization is done, you can always recover.

Run two instances of the program. Work in one instance and view the Exhibit Log in the other instance. On the TMG Tips site, there is a Side-by-Side layout designed to use when running two instances of the program. http://www.tmgtips.com/layouts.htm

The problem with recommending such an approach (synchronization) is that a user who didn't understand the limits would destroy his/her database if it were edited on both machines and then synchronized in both directions.

You should change the sentence for the Note tag to: You must have a sentence structure and this will print the memo as is. Why? You can add as many Note tags for a person as you wish. You can date them or not. You can position them as you wish chronologically using the sort date. You can control the output with the sentence structure. You can annotate them with citations and with embedded citations as necessary. (That'll never happen in any event. It's a violation of the first rule of how TMG is designed. In TMG, data is attached to individuals by using tags and flags. Tags include names, events and relationships... Note tags (which can be named anything that you wish) are 'events' in this context.)

Just to be clear. In TMG, a Marriage event is just like all other events. There are no special internal or external (MRIN) IDs for marriages. As John says, you could use the Reference field with the same value entered for both spouses. Of course, that would preclude using the Reference field for any other purpose. You could create a MRIN tag type (probably best in the Other tag type group) and devise an appropriate sentence structure and use the sort date to have the MRIN tags follow the marriages and record the MRIN in the memo field. You can use the List of Events report to get a list of all Marriage events. Filter Tag Type... Label = MARRIAGE END Options Output Columns tab (something like) Tag Type label Prin1 Last, Given Prin1 ID Prin2 Last, Given Prin2 ID Sorted 1 on the Prin1 name or ID and 2 on the Prin2 name or ID. You would have to create and maintain the MRIN values yourself. All in all, I can't see this being a very productive use of your time.

Note that I posted an explanation for the GEDCOM export error above.

There is no such thing as source #0. If, for some reason, a citation is not linked to any source, it will show a 'link' to source #0 (which means the absence of a link).

Yes. The license agreement says that you can do that as long as you only use one installation at a time. The normal procedure is to back up your project on the current machine and restore on the machine you are moving to. Then repeat the process when you move back to the original machine. Ad infinitum. You just need to keep track of which machine was last used for editing your data. It's a good idea to have both machines set up with the exact same data file folder arrangements so no path adjustments are needed when you move from one machine to another. Also you can keep your exhibits current on both machines outside of TMG. When you backup for moving between machines, you should only need to back up the data files, accents and filters and nothing else. That makes the process faster and holds the size of the backup file down.

This GEDCOM export error should be fixed in v7. I'm still looking at the specific issue to see if I can figure out a work-around for v6.12. The problem is that two source element groups were added (Citation Memo and Repository Memo) and the GEDCOM export code was not updated to deal with these two additional source element groups. So... If you have any source that uses a source type or locally edited source output template which uses either of these two source element groups, you will get this output error. The only work-around for v6.12 would be to remove those source element groups from any output template that uses them for all sources that you plan to export. Maybe putting them in sensitive curly braces would work as a temporary fix.

This is a program error that has to do with the Add Person function. You didn't give any step-by-step as to how you got this error. I have no ideas why you would also be having any performance issues. You need to call or email Support and let them work through this with you.

What does this have to do with the questions asked in the first post? If you want to copy selected individuals from one data set to another, there is no need to get into merging data sets. After the individuals are copied, you can then merge any duplicate individuals if necessary.

Merging projects does exactly what you want to do. It copies data sets from the source project into the target project. I have no idea why you would think that's something to be avoided. It makes absolutely no changes to the data sets in the target project that existed before the merge.

You should both be using TMG v6.12. The important thing is to preserve the original data by making backups. The following will give you the general idea. Make a copy of her project. Edit that copy and use the Data Set Manager to delete any unwanted data sets so that the project only contains the data set that you want. Merge that project into your project. That will add the data set from her project as a new data set in your project. Copy the individuals of interest from her data set to your data set. Make a copy of your project. Edit that copy and use the Data Set Manager to delete any unwanted data sets. Now you have a new project with the desired data set. Check out this tutorial and other topics on Terry Reigel's website. http://tmg.reigelridge.com/merging.htm

The Simple Wizard settings are the same as the Advanced Wizard defaults. With GEDCOM imports, you are almost always going to need to use the Advanced Wizard to assign custom tag types to non-standard, custom, and Event Misc GEDCOM tags. Also, you might want to select settings like assume marriage of parents and cite the GEDCOM for all imported data.

Age is calculated for the Tag Box age column when you add that to your layout. And age is calculated 'on-the-fly' for narrative reports when you add an age variable to a sentence structure. The Age tag, for example, has an age variable in the sentence by default. Keep in mind that there are a couple of sentence age variables that behave differently.

Please read this document. http://www.whollygenes.com/files/tmg6andwinvista.pdf The only version of TMG recommended to run under WinVista is v6.12. And you should use the v6.12 installer, not upgrade installers from other versions. When you buy the upgrade from v5 to v6, you are given a download link for the v6.12 installer. (Actually, you can download the 'trial' version and unlock it with your new v6 registration information.) http://www.whollygenes.com/files/tmg6setup.exe

In the Project Explorer window, right-click and select 'Link Project Explorer to other windows'. There have to be links from you to your parent and from your parent to your grandmother. Check your Person View to make sure that your parent is the appropriate primary parent and check your parent's Person View to make sure that your grandmother is linked as the primary mother. If you started from you and added your mother and father and then, from the appropriate parent, added his/her mother and father, that would have created the necessary primary links. Also make sure that one of the links is not there but non-primary. Ask on the v6 forum if you can't resolve this (since you can't respond to this message).

Only for place searching through the [Place Info] button ("Look up this place on the web"). The parameters can be customized through the placeinfo.txt file. The people search needs to be redesigned to use a similar open user-customizable method. We have discussed that since the Ancestry issue came up. Such a change won't be done for v7.0 but maybe for a subsequent v7 update.

Back up each project there. Once this is done (and you are sure that you have backed up all projects, delete all files in the projects folder. I would suggest that you then make a TMG data tree in My Documents or elsewhere in user space. You can, for example, relocate My Documents to user space if you wish. Under the TMG data tree, add a projects folder and under that, add a folder for each project so each project has its own space. For example, using v6.12, I have relocated My Documents and have an arrangement similar to this. (My Documents is called Documents under WinVista.) D:\User_data\My Documents\ D:\User_data\My Documents\TMG_data\ D:\User_data\My Documents\TMG_data\projects\ D:\User_data\My Documents\TMG_data\exhibits\ D:\User_data\My Documents\TMG_data\backups\ D:\User_data\My Documents\TMG_data\timelines D:\User_data\My Documents\TMG_data\export\ D:\User_data\My Documents\TMG_data\configuration_files\ Under the projects folder is a different folder for each project. Once you are set up, restore each project to the appropriate folder. You edit your Preferences paths to fit this arrangement. Note that this means copying the timelines the timelines folder above. And relocating exhibits if your exhibits are in the program folder. This isolates your data from the program folder and makes it easier to back up... as well as following the operating system rules about not puting user data in the program folder. If you relocate exhibits, you can use File / Maintenance / Validate File Integrity and it's exhibit feature to relink the exhibits to the projects.