By Buck - Wednesday, September 21, 2005
|
The following is the message I receive when the report generation process aborts:Error at line 334 (individual.htm) generating 'ind08123.htm': Object doesn't support this property or method: 'e.school.Pictures' Microsoft VBScript runtime error 800A01B6 |
I know that it is associated with pictures that were added, but how do I trace where the problem is located? The pictures display with no problem in the program itself. Thanks. Buck
|
By GenoProSupport - Wednesday, September 21, 2005
|
Can you try generating the report using Beta 14b?
|
By Buck - Wednesday, September 21, 2005
|
My current version says it is the latest and will not download 14b. I will go to the downloads section to see if I can bypass this download problem. Thanks
|
By GenoProSupport - Wednesday, September 21, 2005
|
Buck (9/21/2005)
My current version says it is the latest and will not download 14b. I will go to the downloads section to see if I can bypass this download problem. Thanks The Beta is not part of the Auto Upgrade dialog. You have to manuallly go to http://www.genopro.com/beta/ each time you want to upgrade.
|
By Yehudad - Wednesday, September 21, 2005
|
Buck
My current version says it is the latest and will not download 14b. I will go to the downloads section to see if I can bypass this download problem. Thanks The "check for update" feature is not working on the beta vesion. Dan explained it a few days ago. I will try to find the thread. You have to go to the beta page and check for updates yourself.
|
By Buck - Wednesday, September 21, 2005
|
I installed 14b and am still receiving the following message: Error at line 72 (individual.htm) generating 'ind08123.htm': Object doesn't support this property or method: 'e.school.Pictures' Microsoft VBScript runtime error 800A01B6 | I repeat: where do I look to find the bug in this code? Thanks. Buck
|
By GenoProSupport - Wednesday, September 21, 2005
|
You need to edit the report skin and look at the file individual.htm. This is very strange, because I personally generated over one million HTML pages using the report generator and never got this error. Any .gno and .ged file I have on my hard drive have been thru the report generator. If you send me your .gno file (by email), I will generate a report and see where the problem is.
|
By Yehudad - Wednesday, September 21, 2005
|
Are you using your own skin or GenoPro's default skin? If you are using your own, try to compare with the default individual.htm file what method had been changed if at all. Again Dan was ahead of me by an inch...
|
By Buck - Wednesday, September 21, 2005
|
The problem is associated with the "Permanent ID" under the Report Tab on an individual's properties page. If you erase the Permanent ID and then click next, the problem moves to later in the generate process. The tree that I had built was comprised of parts from other GenoPro trees. I have had this problem before, but thought it a fluke until today when I have been unable to eliminate the problem entirely. Any thoughts or ideas? Buck
|
By GenoProSupport - Wednesday, September 21, 2005
|
Buck (9/21/2005) If you erase the Permanent ID and then click next, the problem moves to later in the generate process.The report generator needs the Permanent ID to generate the HTML pages. If you delete this Permanent ID, GenoPro will automatically assign a new Permanent ID with a larger value, so it is normal the problem occurs later in the generate process. Are you generating from the built-in templates from Beta 14b, or from a customized report?
|
By Buck - Wednesday, September 21, 2005
|
I am using the built-in templates. There ought to be a way to regenerate the entire set of permanent IDs. Then, this problem might go away. Buck
|
By Buck - Thursday, September 22, 2005
|
FYI, This bug first appeared on version 2.b13f. It involves the implementation of the "Education" tab in the generated report. Somehow your object is not passing the class information required by "individual.htm". ... "and that's all I have to say about that" (FG)
|
By GenoProSupport - Friday, September 23, 2005
|
Buck (9/21/2005)
The following is the message I receive when the report generation process aborts: Error at line 334 (individual.htm) generating 'ind08123.htm': Object doesn't support this property or method: 'e.school.Pictures' Microsoft VBScript runtime error 800A01B6 |
I know that it is associated with pictures that were added, but how do I trace where the problem is located? The pictures display with no problem in the program itself. Thanks for your file sample. I am able to reproduce the problem on my machine. I am in the middle of a big task and cannot do it now, however I will do it next week.
|
By GenoProSupport - Saturday, October 1, 2005
|
I discovered what the problem is. Your family data was imported from a .ged (Gedcom) file and there are two "conflicting tags".e.school.Pictures e.school._XREF |
This is obviously a bug in GenoPro, and I am working to fix it. Solution: If you really need this fixed, you can edit your .xml file using notepad and remove all references to the _XREF attribute. Save your .xml file and import it again using GenoPro. You will no longer get this error when generating a report.
|
By Buck - Saturday, October 22, 2005
|
Thanks for your response and for finding the bug. However, I might wait for a beta release in which this is fixed. I backed off to Version 2.b13h in order to generate reports (even though I prefer the newer version). However, if needs be, I could use the "XML solution" you proposed until the bug is permanently fixed. Thanks again for your help.
|
By GenoProSupport - Tuesday, June 6, 2006
|
I finally fixed this bug. GenoPro has special code for importing places from a Gedcom file. The problem was the keyword School is also a place, however GenoPro was not handling the _XREF for that keyword. Beta 16b fixes the problem by handling _XREF for the School tag.If you have this error, use Notepad and edit the XML file to remove any custom tag having names with _XREF . Then, open the XML file with GenoPro and you will have your genealogy tree back, without those erronous tags. Here a typical example of what to remove: <Tags id="Education"> <TagData name="SCHOOL._XREF"> <displayname>SCHOOL._XREF</displayname> </TagData> <TagData name="_GEDCOM_ERROR.SCHOOL._XREF"> <displayname>_GEDCOM_ERROR.SCHOOL._XREF</displayname> </TagData> </Tags> |
|