Jim Byram

Kevin, The problem appears to be limited to the E-table (witness table). The problem is that an EPER has records in the wrong data set (DSID). All of the individuals with problems appear to be in data set #2. Your example Anna Maria Schmitz (2:3674) has two records in the E-table... one with DSID 1 and one with DSID 2. Ewen Castor (2:1) has three records in the E-table, all DSID 1. Persons 2:3696, 2:3702, 2:3707, 2:3713 each have one E-table record in DSID 1 and another in DSID 2. These four person records are grouped together. Maybe you can see some sort of pattern? We're trying to make sure that all the records in the $-table (person) have the correct DSID. From looking at the records towards the end of the table, you've been entering new people into both data sets. We've never seen the E-table issue. Have you been doing any particular sort of unusual data manipulations that might be tied to this? If the issue is only an E-table issue, these records can be cross-checked against the $-table and corrected. An addition will be made to VFI to check for this sort of data issue and make corrections. Update: The same DSID issue is occurring in the NPV-table and this explains the name loss with merge. Update: Code has been written to repair this and I've tested it on your data. I can now repair your project and sent you an email requesting your current project to fix it. Jim

That suggests that a configuration setting that you made is the cause of the problem. Can you try to replicate what you did and determine which setting?

John, Any issues with the RootsWeb mail list should be conveyed directly to Lee Hoffman. Jim

The simple workaround is to create a custom Probate2 tag in the Other group and use that.

The simple answer is that each data set is in a different box by design and there are no data manipulations between data sets. This is unlikely to change.

The error is either the result of some export configuration selection or a data issue. Have you tried the default export configuration (which is GEDCOM 5.5 with the ANSI character set)? Please detail any changes from the default export configuration so those can be tested.

The translations and language adjustments evolve with every version of the program. For that reason, you want to be running the latest version of the program. v6.07.000 is a very stable release. The only problem of note is an error when adding tags in Beginner Mode and you can click by the error or switch to Advanced Mode which doesn't have the error. I would suggest taking advantage of the v6 registration that you already have and updating.

Kevin, You should have been advised to revert to a backup with your initial report. And to hold off merging until the source of the issue could be pinned down. You should also update your installation to v6.07 if you have not done so. I've replicated the data set merge issue with your project and am looking at it. One of the programmers is also looking and the issue appears to be damage in your original project but it's taking a while to understand exactly what is happening. Jim

I'm not seeing that. Click on General and I get Tag Type Definition: General. Click on Roles and Sentences and I get Tag Type Definition: Roles and Sentences. Click on Other and I get Tag Type Definition: Other. It looks like the TMG.cnt file is the key to the links. Send me an email and I'll send you the file. Click on the link below for my email. Jim Byram

To anyone who gets the 'not a valid PJC' message. Immediately exit the program. Send me the PJC file from the project that gave the error. I want to examine the file at that state. Contact me by email by clicking on the link below. Jim Byram

David, The Book Manager could be better named. It's a tool to run multiple reports in succession. It could be used to construct a book using Word's master document feature, for example. I use it to run a series of List of People reports to set the flag used for Second Site output. This requires four LOP reports being run in succession for what I want to accomplish. Using Book Manager, it can be done by running one Book Manager report.

It works fine for me. The first time that I selected a custom flag, the Column Type field stayed blank although the Heading field was correct. I needed to reselect the custom flag for the Column Type. After that, with the same report, the custom flag selections have worked on first try. Make sure that the column widths are not exceeding the page width and the output is not wrapping. The custom flag can be 'hidden' (meaning easy to overlook) if wrapping to the second row.

I don't see that. All in my files are exported as FORM JPEG. Can you see a pattern? I asked the programmer to check the code and see if he can come up with a reason for the variability. Note that .TIF files are being exported as FORM TIF rather than FORM TIFF. Both JPEG and TIFF are antiquated forms. You don't see many files saved as .JPEG and .TIFF these days. Export has been extended beyond the specs and should now support all external filetypes supported by the Exhibit Log. The FORM is taken from the filetype. This would make JPEG (as opposed to JPG) an exception.

The problem is with tags exported as individual attributes when the memo is excluded. Not just the memo but the entire GEDCOM line is removed from the output. 1 RELI Christian 2 DATE (some date) 2 PLACE (some place) 2 SOUR (some citation) "Christian" is from the memo field. You exclude it and the output should be: 1 RELI 2 DATE (some date) 2 PLACE (some place) 2 SOUR (some citation) What is happening is that the 1 RELI line is dropped from the output. If the Religion tag had only an excluded memo and no subordinate data at all, then it would be correct to drop the entire line.

Mike, I need to see your project, the GEDCOM, and a description of the examples that you are looking at so I know a person or two to check. You can contact me by email by clicking the link below: Jim Byram

You got me. Don't see that. There was a bug of this nature that was fixed several versions ago. If you have a custom Add Person template, I would reset the template and make a new custom template. It might also be worthwhile to delete the REPEAT*.* files in the program folder to reset those.

If the tag has a date of Bet 1940 and !960 and a sort date of 1940, it will sort on 1940. Sorting is based on sort dates. Tags with no sort dates sort to the beginning or end of the list or don't sort based on the Preferences setting. File / Preferences / Program Options / Tag Box / Undated tags sorted selection Note that name tags can be sorted differently. See the 'Names tags sorted' option under the above option. There is no alphabetical sort option for the Tag Box.

List of... reports should use the selected program date format for output. File / Preferences / Program Options / General / Date format field

Virginia just cracked this. You get the error in Beginner data entry mode. The work-around is to switch to Advanced data entry mode. (Preferences / Program Options / Data Entry tab).

Under My Controls, on the lower left, you can change your password. I think, that if you are signing in, you can have your password emailed to you? If you need to have your account killed so that you can create a new account with the same email address, that will need to wait to next week after the cruise.

No. GEDCOM has always been the only means of exporting data for import into other genealogy programs. You would probably run into legal issues real quick if you exported in another program's proprietary format.

Astrid, I tried an external text file as a primary person exhibit with output to Word. It worked and that might be useful. I also tried a WMV and nothing was output. So some exhibits that can be marked as primary aren't actually output. Jim

No. Not until a version of Foxpro supports Unicode and TMG is updated to use that version of FoxPro.

There should be no relation between the two. The note field on the Supplemental tab should always be exported to a NOTE tag subordinate to the source. I just tested this and it made no difference to whether the note field was exported as to whether a source was linked to the source or not. ???

This issue should be fixed in v6.07.000.