The only way that I have done this (in the FTM world) is by exporting GEDCOM, updating the RAW GEDCOM data by creating two families (one for each union with the appropriate pointers in the data) then reloading the GEDCOM. A job that takes some understanding of GEDCOM.
The display side of FTM for this configuration works well by showing two marriages (and sets of shared facts) each preferred. PAF does a better job of letting you create a 2nd family with the same "parents". What you get is 2 People, 2 Families, 2 Marriages (sets of shared facts).
Silverfox said: "I wouldn't want to have two entries for the same person in my database."
I agree 100%.
So this is another bug that someone should open with FTM.
...EDIT..
I just tried the "Family Group Report" for this configuration and it does not report on the secod marriage correctly. The GUI display does work but the report only uses the first marriage.
The display side of FTM for this configuration works well by showing two marriages (and sets of shared facts) each preferred. PAF does a better job of letting you create a 2nd family with the same "parents". What you get is 2 People, 2 Families, 2 Marriages (sets of shared facts).
Silverfox said: "I wouldn't want to have two entries for the same person in my database."
I agree 100%.
So this is another bug that someone should open with FTM.
...EDIT..
I just tried the "Family Group Report" for this configuration and it does not report on the secod marriage correctly. The GUI display does work but the report only uses the first marriage.