At 8/17/2015 03:37, John Hanson wrote: >Two datasets in the same project does seem the more logical and the reason >for importing it into a separate dataset of course is to make it easier to >tidy it up first. Just for the record, during an import of data from any other source, the data must go into a new data set. If the data then needs to be part of an existing data set, it may be merged into the other data set. >Now to fine an easy day to find the people that appear in both sets! [I think your keyboard may be playing with you. <VBG>] I find a good way is to locate the same person in both data sets is to have both data sets enabled and filter the Project Explorer to show just those persons (and other related persons) -- say something like: Is an Ancestor of of ID # [?] OR Is an Ancestor of of ID # [?] END I almost always use the "[?]" Value in filters as that allows me to quickly change my mind as to the desired focus persons. In the case of a filter like this with multiple data sets, the vale entered would be like "1:1" and "2:16" (no quotes) where the data set ID# is the leading part before the separating colon. If you just enter the persons' ID#, TMG will ask for the ID#. The above may not be the best filter for you, but there are many others that will make the PE show a smaller subset of the people in the two data sets. This will allow you to easily look at and compare the similar persons from both data sets. A Focus Group is another method. The advantage of the PE is that the arrows at the top of the PE allow you to easily "step through" the persons in the PE. Lee