Jim Byram

Just to make sure you understand. The Picklist filter does not carry from one session to another. When you close and reopen the program, the Picklist should be unfiltered. As to the prompt to load the former Picklist filter in the Project Explorer when you start the program. just click [No].

You understand that excluded and sensitive data can already be displayed in the MPL? Preferences / Program Options / Tag Box / tick Show excluded data

The strings files are a FoxPro table just like all the other TMG DBF files. You really need to talk to one of the translators who are the experts on the tools and methods used to implement a language in TMG. I wrote a message to the beta list asking if one of the translators would check this topic and get in touch with you.

Here's an update regarding WinVista and TMG v6.12.000. http://www.whollygenes.com/files/tmg6andwinvista.pdf

The design rule has always been that double-excluded data only show on the edit screens -- Tag Entry and Edit Place. However, the MPL is a place where users evaluate their place data to get the big picture. Having places with double-excluded data hidden makes that difficult. I don't advocate displaying double-excluded data in the MPL but perhaps there should be an indicator to show that a place has double-excluded data. A marker for the row or coloring that row? Better idea. Since the data is parsed to build the list, substituting a placeholder rather than omitting the double-excluded data would add little overhead. Something like: "(--excluded)"

This is a known issue. Import from the Welcome screen. Use: Welcome / Import Don't use: File / Import

Try this. With TMG closed... Go to the program folder and delete strings.cdx. Run TMG and that will trigger a strings reindex. Then check the performance issues.

List of Tasks report

Peter, This was never intended as a look up tool but rather as a tool to add to or edit the table. Jim

This is discussed in an earlier topic; http://www.whollygenes.com/forums201/index...?showtopic=4606 The message is a valid message but why you might get intermittent occurrence has not been resolved yet. Some changes were made in the code and those changes first appear in v6.10. The users who tested this found that Virginia's suggestions worked to eliminate the intermittent occurrence. Make two Preferences changes. Preferences / Program Options / Startup and Exit tab 1) Unselect the Show Tips and Hints option 2) Set the 'Check the website for an update every __ days' option to 0 (zero) days.

Sure. List of Events report Filtered group Add a filter Place Contains (best to use one word for the value) END (You can enter anything for the value but these is less chance of error if one work is possible. Note that this filter will search all place fields. Instead of Place, you could specify any particular field but Place has wider possible usage.)

I can't really answer your question but have some suggestions. One of the WordPerfect experts will find this topic eventually. Issues of this type are often data-related. Keep that in mind and check around the failure point. Which WordPerfect output file type in TMG are you using? If you are using the 'WordPerfect v8 or later' output file type, I'd try the 'Wordperfect v5.1 or later' output file type. When you make a problem report of this type, you need to specify all changes from the default report options that you are using. And last... Have you tried to reset the report to defaults (by clicking the [Delete] button on the report definition screen) and retrying the report? Then, if that works, add the option to output sources as footnotes and try that. Using the 'Wordperfect v5.1 or later' output file type, I was able to print a successful report with 4511 footnotes that completed in the 9th generation. I has problems trying this same report with the 'WordPerfect v8 or later' output file type.

As far as I know, it has never been intended as a lookup system. Offhand, it does two things... assuming that you complete your place data fields by spelling things out (as is good standard practice). 1) With some reports, it can substiture the abbreviation for the full name saving output space. In something like a pedigree chart with very limited space, this feature makes a big difference and is enabled by default. 2) When doing placeinfo/placemap web searches, the table can be used to substitute data for variables so that the website gets the appropriate type of data for its search mechanism.

Seems to me that you're asking for a function that you already have. Why don't you use the Focus Group? It's designed to do exactly this. Navigation using a Focus Group is just as fast as using a bookmark. You can sort the list in the Focus Group various ways. Create a layout which includes the Focus Group. Save each of your groups so that you can recall them.

Don't have any good ideas at this point. How are you navigating to the date and place fields... mouse or keyboard. Where is the mouse cursor located when you type a character?

I haven't seen that and just retested the v6.10 installation process but it sounds like a permissions issue. See my note above that you need to do the first run of TMG after installation as administrator. If fact, with the current WinVista builds, you need to set the TMG shortcut to run as administrator on the Compatibility tab and run TMG as administrator all the time.

It's a bug and we're looking at it. It's not end of sentence spacing in the memo... it's any multiple-spacing within the event tag output stream. For example, put two spaces between two words in an event memo or between two words in an event tag sentence and those are converted to a single space on output. This worked correctly in v6.09 and has been broken since. Update. Fixed and tested. Should be in the v6.11 update.

Would you send me a backup of your project (project files only) to test and tell me which people to test. Click on the link below for my email: Jim Byram

Sherry, Got the same import errors that you did. I then repaired both Generations databases in Generation 8.5a. And was able to import both databases. The import issue was the Generations databases. I've mailed the repaired Generations databases and the TMG projects created from importing the databases to you directly. Jim

A beta tester got this and it's been reported to the developers but we still don't have any idea how to replicate it. I've generated dozens of reports in the last week without the error.

As Virginia said... There is a bug in v6.10 previewing source templates on the Output form tab of the Source Definition Screen when you have TMG set to a language other than English (U.S.). This has only to do with previewing source templates on the Output form tab and has absolutely nothing to do with printing a report. The bug should be fixed in the v6.11 update.

The NOTE tag is not treated any different than any other tag in the Other group. As with any tag in the Other group, you simply create additional custom tags like the original - Note, Note1, Note2, Note3, etc. You can have only one primary of each type but this allows you to have as many primary note tags as you wish.

Not automatically since that is what you appear to be asking. I can't envision any way to do that within the design. However, you can do it exactly like you would add any other source data. Use an existing or custom source element. Add that to the Bibliography templates. Enter the source number as data on the source General tab.

There are a wide variety of issues in regard to running TMG under WinVista including the Tlist issue. Refer to the existing topic. http://www.whollygenes.com/forums201/index...?showtopic=5882 TMG WinVista-compatibility is an active development topic.

The reason for the high VFI count for the first run under v6.10 is explained below. This one reason will account for most or all of the new VFI 'fixes'. Blank dates/sort dates in the tables should have a dummy date value entered into the field. In many cases, the fields were actually left blank. This didn't cause any program errors because the code treated both conditions the same. However, we have spent considerable time identifying and correcting anomolies in the tables and this was one. There was code being written that would be cleaner and work faster if all data/sort date fields with blank dates contained the same dummy 'blank date' value. VFI now corrects this. There is likely still code that leaves blank date fields rather than entering the blank date value and we're still tracking those down and fixing them when found. As Bob said in the change log and newsletter: "It is not unusual and no cause for concern if the first use of VFI in v6.10 produces many "fixed" issues that were not previously reported."