[Phpgedview-talk] Remote linking -- still unclear

[Sergei H. <se...@se...>]

Hi,

after reading the forums and the archives of the mailing list, it is
still somewhat unclear to me what is the proper way to do proper
remote linking.

First, I'd like to explain my ultimate goal:

I'd like to separate the ancestors of the husband and the ancestors of
the wife in two different GEDCOM files. Their common family (incl
descendants) I'd like to put in a third file.
Their family and descendants should be visible from all three sides.

[here I'd like to hear if it is possible at all, but according to the
forums it is a quite common scenario]

I started playing by creating a GEDCOM with a male individual A and
parents FA and MA
and a second GEDCOM with a female individual B and parents FB and MB.

First test was to "remote link" from A to B, remote person B being A's
wife. That creates
a family in A's gedcom, where I can put all the information on the
family, like date and place of the marriage and so on.

But, when viewing from B's GEDCOM file, there is no family visible.
If I create the remote link from B to A, this creates a family record
in B's file, which is not related
to the one in A's file.

I didn't yet start adding children, but this already sounds complicated.

Am I doing this the proper way?
---------------------------------------------------------
The second approach would be to create the "common" part of the tree
by hand in the gedcom files and upload them, but I'd like to hear from
the experts first, If my approach would be correct.

files: A.ged, B.ged, CHLD.ged

put A and all ancestors of A into A.ged, B and ancestors into B.ged
create "stub" individuals A,B in CHLD.ged (with RFN to the other GEDCOMs)

create a Family A+B and children (as individuals) inside CHLD.ged

so far, starting from CHLD, we should see all of the ancestry. but
when coming from A.ged,
should we add a "stub" individual pointing to the person B in file
B.stub and a stub family pointing to the family A+B in gile CHLD.ged
??


Thanks in advance,
Sergei