Greg, I understand your comments if the only weeks that could be involved were from the trust. However, the reservation could have also been with any of the legacy weeks that could have been exchanged that year for DC points.
BocaBoy,
I agree -- the reservation must have been from legacy weeks exchanged that year for DC points -- total agreement.
My (poorly stated) point is what is the probability that the same legacy week units were redeemed that were have to occur to allow a connecting reservation in the same unit.
As an example, if the system was operating the way Sue believes it does, then in order for my example to happen, the owner of [4206] for Week 19 must redeem for points, and the owner of [4206] for Week 20 must also redeem points -- and both units must be redeemed early enough for the reservation to be there in mid-June 2015.
Since there are 22 3BR units, the probability of any individual unit be redeemed is 1/22. So the probability of [4206/19] is 1/22 and the probability of [4206/20] being redeemed is 1/22. The probability of both units being redeemed is 1/484 (ie, 1/22 X 1/22).
And it happened three times in May. So three times in May the 1/484 happened? I think it is far far more likely that the 3BR in Week 19 and the 3BR in Week 20 are in different units and the system doesn't recognize that these are different units because it is a points overlay over a fixed week system.
I wish I could state it more clearly. Marriott needs to solve this with a disclosure both at the time of the reservation and on the confirmation, so that the the person making the reservation understands the risk they are taking at the time of the reservation, and can choose to/to not complete the reservation.
Best,
Greg