Jump to content

Susan J.

  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Gender
  1. Error in LOW report

    There is another speed bump in this workaround - the limitation in the number of rows in the Excel v. 5 output. A list of all witnesses is limited to 65,536 rows, so if the database is large enough to trigger the original "too large" error message, the number of witnesses is probably greater than the 65,536 rows. This limitation does not seem to exist in CSV output, so that output should be used in these "List of All Witnesses" reports. Any Excel version, 2007 and later, opens this report with no problems. Michael and Jim, do you find the same thing? Sue Johnston
  2. Error in LOW report

    Hi Michael, The workaround is more than simply using spreadsheet output. The use of any filter, regardless of output destination, generates the error if the number of witnesses in the project is large enough. I don't know what that "large enough" value is. The workaround involves generating a list of all witnesses to a spreadsheet and then sorting, selecting, filtering the resulting spreadsheet. This means that all filter options must be among the output columns in the spreadsheet report. I'm currently revamping my LoW reports with this in mind. To date, I've found only one problem. Although the LoW report filters allow filtering on any flag, the LoW report columns only allow standard flags. That does away with the utility of a Temporary flag for these LoW reports. I haven't used the Descendant/Ancestor Interest flags in many years, so I will probably treat one of them as a temporary flag for these reports. I can update you if I discover other speed bumps. Sue Johnston
  3. Error in LOW report

    Thank you, Michael and Jim, for working on this. Like you, Jim, I can create an Excel report listing all witnesses with no problems, so I have already started restructuring my currently filtered LoW reports so that I can filter, sort, etc., the list of all witnesses to get the result I want. As long as it's not a problem with my database, and I can use this workaround, I can live with it. Thank you again for testing this. Susan Johnston
  4. This week I discovered that my various LoW reports when run in my main database generate this error message: "... \appdata\local\temp\[alphanumeric string].tmp is too large" and I must exit TMG. I was able to run the reports in the sample project and in various client projects. Lee Hoffman was able to duplicate the error in his large project, but not in smaller projects. Regardless of project used, and regardless of output destination, LoW reports with subject ID # checked worked and LoW reports with subject "All witnesses" worked. All LoW reports with filtered subjects failed in my main database, but not in my smaller databases. Lee had the same results. At one point in my experimentation, I did get a FoxPro error message that began: "Fatal error: Exception code=C06D007E ..." and continued with a list of various "Called from" lines. I have run repair; I've restored the report defaults and created reports and filters from scratch with no changes in these results. I think this might be the result of the way memory is allocated in this report, but I don't know enough on that subject to make this conclusion. Details of my various experiments: On my main computer: TMG 9.05 under Windows 7; project has 18352 people and 81510 witnesses; first failed report had 9 columns, 610 character line length, output to Excel. When the "Create report" button is selected, the "Please wait" window comes up, then the hourglass, and finally the error message. Reducing column number and line length and changing output did not change the results. The same report, filter, etc. worked in the sample project and in my smaller projects. On my laptop, which is usually about 1 month behind my main computer in research progress: TMG 9.05 under Windows 10; project has 18122 people and 80504 witnesses. The report loads "5028 possible filter conditions" (something I don't see in my failed report), up pops the "Please wait" window, wait is about 2 minutes, and the filter window opens for field value input. I backed up my main computer database, omitting all filters, accents, etc., restored this to a new folder on my laptop, and tried to run a filtered LoW reports. The report failed. The slightly smaller March project still worked. My main project has two data sets in it, and the small set is disabled. Because I've been thinking about moving that set to its own project, I deleted it from the restored project on my laptop, and reran the filtered LoW report (still on laptop under Windows 10). This single-data set project has 18224 people and 81144 witnesses. The report worked! My main computer has more disk space and RAM than my laptop. What have I run into? Thank you for any suggestions. Susan Johnston
  5. Missing tag abbreviations

    That was next on my list of things to try, but right now, I'm not experimenting without expert advice. :-) No, it didn't work.
  6. Missing tag abbreviations

    No, I'm not using any real-time backup, etc. on my project folders. I've been checking out my travel/webinar computer, which also has TMG, to see if it has the same problem. It's database is a 9/19 backup. The abbreviations are there, and edits to English (U.S.) are accepted. Whatever happened to TMG on my work computer happened some time between 9/19 and two days ago. Is there anything from TMG on my laptop that I could use to fix my desktop?
  7. Missing tag abbreviations

    Replacing the strings* files didn't help. The abbreviations are still missing and edits still don't "stick." How do I check the tag types data table?
  8. Missing tag abbreviations

    I have the file, Michael. Thank you. I also have two other strings* files: strings.bak and strings.tbk. Should I delete those, or are they reconstructed when TMG is open/closed or does some other magic thing?
  9. Missing tag abbreviations

    Thank you for your reply, Jim. I can't copy the language_files.zip. I get, "The page you are trying to access is not available for your account."
  10. I tried to run a quick pedigree chart yesterday and discovered that the b., m., d., bur. labels were not printing. Michael Hannah correctly pointed out that this report takes those labels from the General tab on the Tag Type definition screen, and those abbreviations were missing from my English (U.S.) screen. I tried editing this, but the edit didn't "take". The abbreviation disappeared when I closed the Tag Type definition screen. I went through my backups, restoring them to a different project folder, and found one with the abbreviations intact from three days ago. I exported those b., m., d., bur. tags and then decided to experiment a little with the test database. I opened one of those tag type definitions and inspected the sentences for each language, closed the screen, and the abbreviation for English (U.S.) had disappeared! I re-imported those tag type definitions, telling the import to overwrite, and that one tag type was imported, with its abbreviation. The abbreviation again disappeared when I opened the Tag Type definition screen and closed it. Other than using my Enlish2 language for these chart reports, I have no idea how to fix this. The only thing I can think of that might have caused this is that I created an experimental custom language. The abbreviations are in the Tag Type definition in the backup before I created that language. However, the strange behavior when editing those b., m., d., bur. abbreviations happens with that backup. What should I do to fix this? (TMG 9.05, Windows 7)
  11. I love the possibilities in the NarrativeChildren tag, but is there a way to include the superscript generation indicator? The default sentence includes this number, but I can't see a way to include it in a NarrativeChildren sentence. Sue Johnston
  12. Cell length limits in Excel Reports

    I can get the full memo to print in the Individual Detail report, which is a tabular report, but that report has problems, too. (1) I'm using Word 2013 on my new computer, and all chart and table report outputs are garbled, so I now need to go through RTF output first. [Open Office might be fine, too, but I haven't installed it - and don't really want to, just to do an interim report.] (2) There's a lot of work required to turn this report into something that can be used for a chronology for multiple people. (3) The leading zeroes in dates don't print on my system, regardless of the check mark, so, once the prep work has been done to combine multiple individuals into one smooth report, dates can't be sorted without more work - or at least some Excel macro that I haven't developed. I suspect this would be simple, if only TMG offered a more up-to-date Excel version for output! Thank you for trying.
  13. Cell length limits in Excel Reports

    The CSV file has the same 254 character limit - although I didn't test this in TMG v. 9 while I had the 30-day trial.
  14. I would like to create an Excel report that includes TMG memo fields longer than 254 characters. Regardless of the column width I set in the Report Options, the Excel column contents are truncated, and when I return to the Report Options screen, the column width has been reset to 254. I am using TMG v. 8.08 and Windows 7. I use Excel 2013, but of course, the TMG output is to Excel v5. I have no problem with truncated fields when creating spreadsheets directly in Excel 2013, so is this limit a TMG thing or an Excel v5 thing? If the former, are there any plans to increase the column width limit in the TMG report options? If the latter, are there any plans to add a later version of Excel - one that doesn't impose a 254 character limit to a cell - to the report output file list? In testing TMG v. 9, I noticed nothing different in this report. The problem could be me, so is there some option I'm missing? Does anyone have an efficient work-around? Thank you for your help. Susan Johnston