Given your information, I went through my uncle's matches and determined
that the problem occurs with only 3 out of 82 matches. They are neither the
oldest nor the newest matches,.

The problem occurs whenever I select one of these individuals, it doesn't
matter if I select them first or after one or two other individuals have
been selected. Their data does not load and I am unable to "remove" them
from the set to be compared. To get out of whatever loop I'm in, I have to
leave Chromosome Browser by clicking on another link. Comparisons for all
other matches in any sequence work fine.

Sharon

On Tue, Dec 7, 2010 at 11:57 AM, Larry Vick <> wrote:

> Sharon,
>
> I first noticed a problem on September 23rd, and sent FTDNA an e-mail about
> it.
> In my case it only affected new matches. I could use the chromosome
> browser for
> old ones. The problem went away when the next batch of new matches came
> in, but
> then it reappeared the next time I had new a new match. When I was at the
> FTDNA
> conference I asked the IT folks if they had figured the problem out, and
> they
> said they had. I guess there is something quirky that keeps popping up.
>
> Regards,
>
> Larry
>
>
>
>
> ________________________________
> From: Sharon Fontenot <>
> To:
> Sent: Tue, December 7, 2010 12:48:34 PM
> Subject: Re: [DNA] FTDNA still not working
>
> Hi Larry -
>
> It seems that my Chromosome Browser problem does not occur with all
> matches,
> but with at least (or only) one. Since my uncle just has 82 matches, I
> should probably go through the list trying three at a time and find out how
> many this matches have this problem, and report it that way.
>
> Sharon
>
>
>
>
> -------------------------------
> To unsubscribe from the list, please send an email to
> with the word 'unsubscribe' without the
> quotes in the subject and the body of the message
>