GenoPro Support Forum

Home Search Tags Who's On

Welcome Guest ( Login | Register )

bug: custom tag name clash with GenoDate Object

Rate Topic

Topic View

Topic Options

Author	bug: custom tag name clash with GenoDate Object
genome	Posted Friday, May 6, 2005 - Post #6769
Legendary Master Administrators Customers Important Contributors FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1 Last Login: 3 hours ago Posts: 3,487, Visits: 27,238	My initial attempts at using the new report generator were unsuccessful because I kept hitting the following error: Generating report to G:\Shared Documents\Family\Genealogy\reports\ Cloning document Masterb13... Opening configuration file Config.xml for skin '\_English - Generic Report'... Loading dictionary.xml... Processing template 'init.htm'... Processing template 'default.htm'... Processing template 'toc_families.htm'... Processing template 'toc_individuals.htm'... Error at line 72: Object doesn't support this action: 'i.birth.date.year' Microsoft VBScript runtime error 800A01BD After a bit of head scratching I realized that one of my custom tags, used to record the original Gedcom date qualifier, which I had called 'birth.date.type' was causing a problem with the GenoDate object. When I deleted the custom tag, using the tag editor, and saved the file the problem remained, even though the tag had been removed from the .xml file. It was only after I re-imported the .xml file into GenoPro that the report was produced without error. It was as if the erroneous tag remained in the .gno file even after deleting it with the tag editor. I submit this bug in case other users hit the same or similar problem. Perhaps a 'reserved word list' is required to prevent such clashes. 'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Reply
genome	Posted Thursday, August 18, 2005 - Post #6772
Legendary Master Administrators Customers Important Contributors FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1 Last Login: 3 hours ago Posts: 3,487, Visits: 27,238	The idea was to capture Gedcom date modifiers such as ABT, BEF, AFT, EST, CAL etc. I.e. type of approximate date. I know this area has beeen covered elsewhere in the forum and is a planned enchancement to GenoPro. 'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"

Threaded View

Threaded View

bug: custom tag name clash with GenoDate Object By genome ( Friday, May 6, 2005 )

Beta 16 will have this built-in. New methods will be added to the... By GenoProSupport ( Thursday, August 18, 2005 )

The idea was to capture Gedcom date modifiers such as ABT, BEF, AFT,... By genome ( Thursday, August 18, 2005 )

From the attachment you sent, I see what you mean. This is a though... By GenoProSupport ( Thursday, August 18, 2005 )

Can you send me a sample .gno file producing the error. I will take a... By GenoProSupport ( Thursday, August 18, 2005 )

Reading This Topic

GenoPro Support Forum

bug: custom tag name clash with GenoDate Object

Threaded View

Similar Topics

Reading This Topic