I have found that when generating a descendant report using NGSQ numbering in FTM2012 that the NGSQ number assignment generator algorithm "uses up" extra numbers when there is a child from a marriage of first cousins. In essence, the algorithm appears to assign two numbers for the child, when traversing the tree from the common ancestor. In the descendant report, the first of the two numbers is reported for the child, however the second number goes unused in the report. The problem is compounded if the child from the marriage of first cousins has further children as more NGSQ numbers go unused for each of them too (and so on). This "bug" can cause difficulties when comparing reports generated from earlier versions (such as from FTM around 2005) in which the software properly detected this condition and did not "use up" extra number assignments. Is there a workaround?