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

GenoPro Support Forum




Data corruption of custom tag information when copying from one .gno...

Click to view RSS...
Author
Posted Monday, February 11, 2019 - Post #39247
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

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

Last Login: 15 hours ago
Posts: 2,775, Visits: 20,129
I've been struggling with a problem that has hindered a project I am presently working on to merge .gno files.

I have discovered that when I copy a genogram from one .gno to another then custom tag data from the source objects get duplicated into different tags in the target file.

e.g. Take an example a.gno (see attached) with Individual custom tags tagA1, TagA2 & tagA3
http://support.genopro.com/Uploads/Images/bdef2ff9-9a46-4bb2-8d0a-0aa1.png


Then copy the contents of a genogram with different Individual custom tags tagB1, tagB2 & tagB3 from another b.gno (also attached)

http://support.genopro.com/Uploads/Images/ff8f4e7e-117f-4418-863e-eb56.png


we end up with the inserted Individuals having tag contents from tagB1/2/3 duplicated into the custom tags tagA1/2/3 !

http://support.genopro.com/Uploads/Images/9aaa7db6-e545-4d32-8943-58a5.png


After a lot of head scratching I found a work around to avoid this.  Before copying b to a, copy an Individual from a to b, thus copying custom tag definitions of a to b. You can then delete (not undo)  the individual from b leaving the custom tags definitions in place.  
Then when you copy from b to a no duplication occurs.

This duplication can occur with any object type, Family, Place, Source etc. so it is necessary to apply the above work around to all object types involved in the desired copy process.

This is tedious so would be nice to have a proper fix in GenoPro for this.

I have now created a .gno that has every GenoPro object type within it (see work around.gno attached).
http://support.genopro.com/Uploads/Images/5f6ea082-91ce-4075-8c67-d778.png
This can be used as the work around by copying it into the target .gno then copying it from the target to the source .gno . This action 'sucks up' all custom tag definitions and adds them to source so no content duplication occurs when copying objects from source to target.   Should be carried out using a 'throw away' copy of the source as the custom tag definitions will otherwise persist there. 


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


a.gno (3 views, 1.00 KB)
b.gno (0 views, 994 bytes)
work around.gno (0 views, 1.78 KB)


Tags:

Edited: Monday, February 11, 2019 by genome


Similar Topics

Click to view RSS...
Expand / Collapse

Reading This Topic

Expand / Collapse