I'm trying to make sure I understand what you mean. With a census as an example, do you mean you would create a census fact for the head of the house, then share it with everyone listed adding their custom census notes. Then you would also go to each person and make an individual census fact with the same info? Kim On 11/05/2012 01:17 PM, Tom Holden wrote: > Laura has another suggestion or practice to get around the limitations of GEDCOM while taking advantage of RM's shared fact virtues in its reports. The idea is to use a custom fact type as a shared fact while, at the same time, a standard unshared fact type carrying the same information for each sharee. The standard individual one is included for export but excluded from reports. The custom shared one is the opposite, excluded from GEDCOM but included in reports. > > It's more effort but maintains highest compatibility with third party programs while fully exploiting reports. Clever! > > Tom >
Well, I don't but that is my interpretation of a workaround that Laura came up with. As to a shared-to-unshared conversion tool, I believe that the iPad app GEDview does that on its opening of a GEDCOM from RM. If it does it well, that might be a solution for some. Tom On 2012-11-05, at 3:00 PM, Kim <kim.mills@wightman.ca> wrote: > I'm trying to make sure I understand what you mean. With a census as an > example, do you mean you would create a census fact for the head of the > house, then share it with everyone listed adding their custom census notes. > Then you would also go to each person and make an individual census fact > with the same info? > > Kim > > On 11/05/2012 01:17 PM, Tom Holden wrote: >> Laura has another suggestion or practice to get around the limitations of GEDCOM while taking advantage of RM's shared fact virtues in its reports. The idea is to use a custom fact type as a shared fact while, at the same time, a standard unshared fact type carrying the same information for each sharee. The standard individual one is included for export but excluded from reports. The custom shared one is the opposite, excluded from GEDCOM but included in reports. >> >> It's more effort but maintains highest compatibility with third party programs while fully exploiting reports. Clever!