GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 

GenoPro Support Forum




Error when running the Narrative Report.

Click to view RSS...
Author Error at line 182, position 12 (Code/Util.vbs) generating 'timeline.htm': Invalid procedure call or argument: 'Left' Microsoft VBScript runtime error 800A0005
Posted Monday, October 19, 2026 - Post #47992
Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer

Customers
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: Yesterday @ 10:05 AM
Posts: 282, Visits: 1,829
I tested removing the commas in the date field on R-P297.

Here is before:
https://support.genopro.com/Uploads/Images/3e260992-47a5-459a-8206-0cf8.png




And here is after I removed the comma in the Date field:
https://support.genopro.com/Uploads/Images/ef4110ec-f2fe-412b-a771-efce.png
Posted Monday, October 19, 2026 - Post #47991
Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer

Customers
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: Yesterday @ 10:05 AM
Posts: 282, Visits: 1,829
Report ran without an issue.

Questions about two cases:

First, the Haplogroup (person) in Green was born in 1500 AD.  His male ancestors (highlighted in yellow) were born in BC dates.

  • Is there a way for the birthdate of J-L283 to appear as b.  ~3900 BC, instead of b. ~ dd MMM 3900 BC.  I see AD dates skip the "dd MMM" before the "YYYY".


https://support.genopro.com/Uploads/Images/5c20ffa7-b4dc-4daf-94e9-103e.png

  • I entered the dates before ~9999 BC as ~10,000 BC.  If I erase the comma.  Will that resolve the issue?  I guess I could test that myself.  EDIT:  I tested it, and yes, removing the commas resolves the issue.  See post below.




https://support.genopro.com/Uploads/Images/5a4d4a70-acad-4762-8c28-8e10.png




Finally, some dates are currently Unknown.  I thought about entering some date closer to now compared to the parent date (by a year or two, or by some prime number) and include some symbol before the year to more easily find these data points.  (The Haplogroup will be younger than the parent, but not sure if it will younger or older than the currently known sibling(s)).  What symbols can I add before the dates?  >?  c.? >>?  others?

https://support.genopro.com/Uploads/Images/884193fb-8569-4c37-93c5-3c0d.png

Edited: Wednesday, October 21, 2026 by NiKo
Posted Monday, October 19, 2026 - Post #47990
Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer

Customers
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: Yesterday @ 10:05 AM
Posts: 282, Visits: 1,829
Thank you Genome!

Apologies for the slow reply!  I replaced the files and am currently re-running the Narrative Report.



I thought the issue felt deja vu ... I tried searching for the previous post using the same error code, but nothing came up.  Strange.



Thanks for the clarification re: valid GEDCOM dates!

I'm debating making a Custom Field for all those dates, so I can display them in the Format I prefer without complicating/killing the Narrative Report.  Any thoughts? Advice?

Most of the dates are Approximate, so I've put a ~ in front of all of them.

Some dates are "Unknown", but I know the date of the previous Haplogroup, so I thought about adding some fixed (prime?) number to previous date, and a unique symbol in front of the date.  For example, the "previous Haplogroup" will have a date of ~0500.  The "son" of the "previous Haplogroup" has an "Unknown" date (it will probably be figured out in the future), so could I use ">0507".  What symbols can I use in front of the date to show they are "Unknown" in the master database?
Posted Saturday, July 4, 2026 - Post #47785
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: Sunday, November 1, 2026
Posts: 3,504, Visits: 27,520
Deja vu on this one, you last reported it 4 years ago https://support.genopro.com/Topic42274.aspx   Hehe

But I have now taken a closer look and have a partial solution in that timelines now accept BC & BCE dates but only with 4 digit years i.e. 9999 BCE -> 9999

At present I do not have the full source of the Simile TimeLine code and it is therefore difficult to try to extend the date range accepted.

The 3 files attached need to be copied to your Common\Code folder replacing existing files of the same names.

Regarding your second query in the same earlier post, I don't think GedCom accepts thousandths separators in integers, so instead of 100,000 BCE use 100000 BCE

Cheers,

Ron


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"


Init.htm (38 views, 76.70 KB)
TimelineInfo.vbs (32 views, 10.43 KB)
Util.vbs (39 views, 125.90 KB)
Posted Wednesday, July 1, 2026 - Post #47781
Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer

Customers
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: Yesterday @ 10:05 AM
Posts: 282, Visits: 1,829
I keep getting the following error:

https://support.genopro.com/Uploads/Images/9db22f36-792a-4226-b77d-878b.png


The Tree I'm trying to generate has the following blurb at the bottom of the Home Page: This genealogy report was generated by GenoPro® version 3.1.0.1 on 2026.7.2 using skin template (2023.09.22) with code base 2024.06.03.

I can't remember if I tried re-generating my tree after installing the latest set of reports this past April.

The major change I made to the tree was adding a genomap with ~500 DNA Haplogroups, most with BC dates in the format "~10,000 BC" (as an example).  

EDIT: I ran the Narrative Report on one Genomap that doesn't have any BC dates on it, and there were no issues.

Edited: Wednesday, July 1, 2026 by NiKo


Similar Topics

Click to view RSS...
Expand / Collapse

Reading This Topic

Expand / Collapse