Yeah, not mine either. :-) But an irritating bug it is. I was having data issues as a result of this and scratched my head until I ran it through debugging and watched some of the data changing. I gave up on a "solution" and just noted it so I wouldn't trust the control values on the fly.

It would be interesting to know what is happening internally here but I don't know how or have the time to deal with it. My guess is that ASP.NET does not update internal flags until later in the life cycle of the page, but that's just a guess.

>Bill,
>
>Well thanks for confirming it ain't my problem lol.
>
>>I have seen this kind of behavior before and could never find out the cause so I think it must be a bug of some sort. I generally use flags to control this kind of logic so I don't run into this problem. MS, ya gotta love 'em. :-)