GenoPro Support Forum

Ron (11/2/2006)

---

The Report Generator does not permit updating of the .gno file so it will continue to produce a new .xml file with a different name to the .gno file, which the user will need to reopen will GenoPro and save as .gno. This approach also provides some level of safety against bugs or inadvent use.

In the future, GenoPro will support updating data field via macros.  I will make sure macros are simple to write and effective to acomplish tasks, such as formatting text, changing display attributes such as color, rename/move data fields and so on.

This is not quite correct, what I said was I will not be maintaining the gnoxml2ged.vbs, the GenoPro XML to Gedcom convertor, because it was being superceded by a Report Generator skin that does the same job.

There is still my other utility VBScript gnoxmlutils.vbs. I am happy to investigate any problems reported with its use. It has an option (no.12) that is not documented on the Web page, to create a custom tag, DisplayDates, that holds the the date of birth if present, otherwise date of baptism (or other Religous Ceremony name) and the date of death, as often the only source of birth information is church records that do not necessarily reecord the date of birth.

It is straightforward to use the GenoPro Display menu to specify a Custom Tag to to displayed above each individual and set the number of lines, the problem comes when trying to maintain the contents of the Custom Tag. My utility can be run from time to time to refresh the contents of the Custom Tag to bring them in line with any changes. E.g. it can be run before Narrative Report Generation.

However I realise it is not that straightforward unzipping the XML file from the .gno and running the script. therefore I intend to move the whole utility into a GenoPro Report Generator skin and perhaps allow the the user to specify which combination of fields he wants generated in the Custom Tag. The Report Generator does not permit updating of the .gno file so it will continue to produce a new .xml file with a different name to the .gno file, which the user will need to reopen will GenoPro and save as .gno. This approach also provides some level of safety against bugs or inadvent use.

May I suggest that someone who knows how to use Custom tags writes an example based on the above request.