For what its worth, I get the same behavior. I brought this up to Kevin and if I remember correctly he said this is not a problem. I will defer to him on this, however, I thought I would let you know that I think this is not a problem. I have not found this to be a problem as I do not need to modify any code in these classes.

HTH


>How do we correct for this problem?
>Our first assumption is that we've just missed a setting somewhere, but have not yet found it.
>Is it possible there is a problem in the MM.Net framework itself?
>
>Any help much appreciated.
>
>Thanks