|
|
|
Grand Master
 
Group: Customers
Last Login: Yesterday @ 6:30:53 PM
GenoPro Version: 2.0.1.6
Posts: 1,151,
Visits: 5,401
|
|
| The error at line 29 of GenoProParser.js occurs when the Microsocft XML Parser fails to load the GenoPro XML data (i.e. the .gno file). This could indicate one or more invalid XML 1.0 characters (e.g. a Tab character Hex(08)) within your .gno file. The English Narrative Report displays better diagnostics (e.g. line number and XML source line) in these circumstances. Could you please try running the English Narrative Report rather than the Descendants Report and report back with any error message generated. I will improve the error reporting of the Descendants Report to cover this scenario. As regards the old error message, I believe this only occurs when a single parent family line is selected. You should still be able to select a family line that has two parents in order to gnerate a Descendants Report for both parents.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Yesterday @ 6:30:53 PM
GenoPro Version: 2.0.1.6
Posts: 1,151,
Visits: 5,401
|
|
petu (7/23/2008)
Trying to generate a meaningful report sucks Pardon My English. What good are the generation Icons on the upper tool bar if they will not work when you try to write a report using them?I do my best to get things right but it is not always possible to test all situations. I rely on constructive feedback to improve the reports and fix bugs. The Descendants Report has been around for some time without anyone else reporting the two problems you have found. Once reported I try to fix bugs as quickly as possible. To this end I have attached a revised Descendants Report that I hope fixes the first of your problems and should provide additional information as to the cause of the second issue. If you care to extract the zip file into a folder below your GenoPro skins folder and then run your report again using this custom skin I will be happy to progress this problem further and achieve a resolution.Maybe you should look at rootsweb.com and emulate some of their reports for your program. I looked at the RootsWeb WorldConnect project reports and didn't see anything special. Certainly nothing that comes close to the GenoPro Narrative Report. GenoPro has similar Descendants and Ancestor reports but with unlimited generations. It lacks a printable Pedigree Chart but a viewable chart is included as part of the Narrative Report. With the Gedcom Export you can of course choose any package you wish to report on your data. However the extra details that can be recorded in GenoPro will not be included.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Forum Newbie
Group: Customers
Last Login: 9/7/2008 6:01:23 AM
GenoPro Version: 2.0.1.5
Posts: 1,
Visits: 9
|
|
I am having the same problem but my error is:
Error at line 13, position 1 (Code/GenoProParser.js): Automation server can't create object
Microsoft JScript runtime error 800A01AD
I cannot generate any reports at all.
Please help.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: Today @ 7:06:05 AM
GenoPro Version: 2.0.1.6
Posts: 825,
Visits: 7,408
|
|
Can you give a bit more detail about your problem? Which version of Genopro; which report skins you have tried and whether you have used the new file Ron posted in the previous message.
It would be very unusual if you can not produce any report at all but this has been caused by non standard characters in the XML file
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Yesterday @ 6:30:53 PM
GenoPro Version: 2.0.1.6
Posts: 1,151,
Visits: 5,401
|
|
wendysmith20001 (8/24/2008)
I am having the same problem but my error is:
Error at line 13, position 1 (Code/GenoProParser.js): Automation server can't create object
Microsoft JScript runtime error 800A01AD
This is not the same problem at all. It is similar to several others that have been reported and is due to a corruption of the Windows Scripting Host installation on your system. This is normally incorrect registry settings such as .dll not registered or permissions on a registry key not set correctly. The error occurs when attempting to create a Scriting Dictionary var oSourceIDs = new ActiveXObject("Scripting.Dictionary");
|
Such problems are often, but not always fixed by re-installing Windows Scripting. For Windows XP try downloading and installing Windows Script 5.7. It may work for Vista as well.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|