Descendant Indented Report

[tkintner 0]

I get "record out of range" while the Descendant Indented chart is in preparation, after I click on "create report". Hitting "ignore" enough times gets the report printed, but I don't know what is out of range. I "initialized the repeat..." and no change in the way the program acts.

 

Tom

[nbradley 0]

Have you run "Optimize" recently (file, maintenance) ?

[Virginia Blakelock 0]

Tom -

 

Try resetting the report configuration to its defaults - using the Delete button under the configuration name.

 

Virginia

[tkintner 0]

After some research.... The problem occurs with the same frequency as the occurence of the State Abbreviation in the report. For example, if the report has 30 persons listed, but there are only 12 occurences of a State Abbreviation in the report, I will get the "record out of range" error 12 times. Clicking on "Ignore" 12 times will eventually print the report. BUT, the state abbreviations are wrong. When it should show WA, I get AK, and the same occurs for ALL of the others, for each of the 12 instances in the report.

 

If I click on "Help" at the "record out of range" error message, nothing happens, certainly no HELP data. Clicking on "Cancel" causes the program to ask me if I want to backup the project. Responding to that question by clicking cancel causes it ask again if I want to backup the project (I repeated this 50 times). When I click "no", TMG terminates.

 

NO other reports demonstrate this result. The Narative version of the report processes in the expected way.

 

I have reindexed, optimized, and validated, all to no avail.

 

Tom

[Virginia Blakelock 0]

Did you reset the report configuration - using the Delete button under the Configuration name on the Report Definition Screen?

 

Is there more information in the error message following the words 'Record out of Range...'? Error messages are saved in the error.txt file in the Logs folder (see Preferences / Current Project Options / Advanced for the location of the Logs folder). Note only the first error message in an event is important.

 

Virginia

[tkintner 0]

Did you reset the report configuration - using the Delete button under the Configuration name on the Report Definition Screen?

 

Is there more information in the error message following the words 'Record out of Range...'? Error messages are saved in the error.txt file in the Logs folder (see Preferences / Current Project Options / Advanced for the location of the Logs folder). Note only the first error message in an event is important.

 

Virginia

 

I did reset the report configuration as you suggest.

 

There was no information after 'record out of range', nor if I chose to ignore a sufficient amount of times that the report would print. If I chose to cancel rather than ignore, TMG terminated (as described above). The ff is the data from the error.txt log:

 

06-01-2010, 12:08:12 1923Object GOREP is not found. 4 FRMRDS_PEOPLE.DESTROY

06-01-2010, 12:10:16 1923Object GOREP is not found. 14 FRMCHART5.UNLOAD

 

I sure thank you for the effort and concern you all are showing.

 

Tom

[Virginia Blakelock 0]

What operating system are you using?

 

If you go to Tools > State/Province Abbreviations, do you get the list of abbreviations and the states look correct?

 

If you uncheck Abbreviate states/provinces in the output, does the report run without error?

 

Try Initialize Repeat Files again, and after that run the maintenance utilities in this order: Optimize / Validate File Integrity / Optimize and repeat that sequence of Optimize and VFI until there are no errors reported in VFI.

 

Virginia

[tkintner 0]

What operating system are you using?

 

If you go to Tools > State/Province Abbreviations, do you get the list of abbreviations and the states look correct?

 

If you uncheck Abbreviate states/provinces in the output, does the report run without error?

 

Try Initialize Repeat Files again, and after that run the maintenance utilities in this order: Optimize / Validate File Integrity / Optimize and repeat that sequence of Optimize and VFI until there are no errors reported in VFI.

 

Virginia

 

This is on Windows Vista, current version.

 

Going to Tools/ State..Abrev: They are correct.

 

Checked or unchecked, the same result occurs. The same result also occurs with both pedigree reports.

 

I optimized, VFI (one error, corrected), optimized once more, VFI (no errors). The reports run exactly the same as before. Moreover, this was a new project. But the older project I have, gives the same result; I've never run these reports before in TMG 7.

 

What can be done to get this fixed? It is really irritating, and I hate to lose the investment I have in TMG, but I NEED the reports to print correctly!

 

Tom

[Virginia Blakelock 0]

Tom -

 

I think we've eliminated the simple solutions. If these reports have never worked correctly in v7, perhaps it is something in your Vista installation. Contact Support.

 

Virginia

[Jim Byram 0]

I don't see any innate problem with the report and state abbreviations. Try this...

 

With TMG closed, delete the shared program data folder. Be sure to delete the entire folder, not just the contents.

"C:\ProgramData\The Master Genealogist v7"

 

Next time that you start TMG, the shared program data folder will be recreated.

 

Now try the report.

[tkintner 0]

I don't see any innate problem with the report and state abbreviations. Try this...

 

With TMG closed, delete the shared program data folder. Be sure to delete the entire folder, not just the contents.

"C:\ProgramData\The Master Genealogist v7"

 

Next time that you start TMG, the shared program data folder will be recreated.

 

Now try the report.

 

I'm a little relunctant to delete all of the shared folder, since it has a lot of graphics (buttons, frames, graphics, sysdata) but I do see where there may be some files that could be responsible for the problem.

 

Does it find all these files somewhere else and initialize them?

 

Tom

[Jim Byram 0]

I'm a little relunctant to delete all of the shared folder, since it has a lot of graphics (buttons, frames, graphics, sysdata) but I do see where there may be some files that could be responsible for the problem.

As I said, delete the folder and the program will recreate it. But this only works if you delete the folder and not just the contents of the folder.

 

This folder is created by the program and will be recreated any time that is missing.

 

The program copies the contents of the shared program data folder from the program folder.

[tkintner 0]

I'm a little relunctant to delete all of the shared folder, since it has a lot of graphics (buttons, frames, graphics, sysdata) but I do see where there may be some files that could be responsible for the problem.

As I said, delete the folder and the program will recreate it. But this only works if you delete the folder and not just the contents of the folder.

 

This folder is created by the program and will be recreated any time that is missing.

 

The program copies the contents of the shared program data folder from the program folder.

 

THANK YOU!! That seems to have fixed the problem.

[Jim Byram 0]

Great. I suspect there was some issue with the abbrevstate database and rebuilding the shared program data file folder fixed that.