Also the GenoPro Report Generator is not likely to be enhanced as all effort is devoted to
Therefore I stick to my original suggestion that .gno files are merged. This could
possibly be automated to some extent. For example take the XML for each .gno and use
search and replace in a text editor to ensure
genomap names are unique by, say, adding a unique prefix for each .gno. This prefix could also be added as the Title tag of each GenoMap entry to serve as the 'volume' identifier, thus allowing the subsetter tool to reproduce the .gno if required. Then the
XML files can be manually merged by copying all GenoMap objects to the GenoMaps section in target XML, Individual objects to Individuals section,
Family to Families section,
Place to Places section etc. For this to work then for technical reasons the first genomap in the
source files must be empty, and so before editing the XML files you would need to, in each .gno, move everything from the first genomap to a new genomap, leaving the first empty. If this is not done then the objects in the first genomap of each .gno will all be placed in the first genomap of the target, as objects in the first genomap are not explicitly tagged with their owning genomap.
Personally I would only use separate .gno for completely separate
family trees, i.e. where there are no
links.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"