"Rick Rothstein (MVP - VB)" wrote in message
Ignore what I said about my timing... I misunderstood your posting and
thought your code measured the time-difference in a single run... I didn't
realize it was a two-step process requiring the bFastTest be flipped
manually for the two cases... the time I reported was the time it took to
run the "chunk" method. I had to break into the "non-chunk" method as it
was
taking too long.

Yes I can see now it was not clear how to test. Although normally in such a
test routine it would compare first one way then the other, but in this case
for most systems it would not be possible to do the second test which would
involve making a union of 20k areas. Hence the comment in the routine to
reduce the range before testing the 'big' union method.

Regards,
Peter T

PS more posts crossing - in future I will wait at least 5 minutes before
responding <g