OK, that sounds good. I'll give these things a try.

Thanks,

Jerry



>>Paul,
>>
>>Thanks. I've been reading other threads on this and I'm willing to use your suggestion but how will I know if this works since I haven't been able to reproduce this? Do you know of a way to reproduce this?
>>
>>Also, do you know if the .Net 3.5 SP1 framework will provide a fix for this? I've read that this includes .Net 2.0SP2 and that this problem is fixed in this service pack.
>>
>
>AFAIK, no, this isn't fixed. It's not really a bug - this exception is basically trying to keep people from messing with the page then submitting the new (modified) version to your site. If it's a case of the user just clicking quickly the problem is that the browser hasn't fully downloaded all of the information needed before the postback occurs - so it compares a set of incomplete data against what it's expecting and fails. Same for modifying lists on the client side.
>
>There isn't a nice simple way of testing this. If it's a heavier page you might be able reproduce it by downloading/installing Fiddler (just Google it), then opening it up and going to Rules > Performance and "Simulate Modem Speeds". Now access the page (if local, access localhost. <- Notice the trailing dot at the end - you need to do this to force the traffic to run through Fiddler's proxy) and try clicking on something before the page has fully rendered (it may take a while to get the timing right). This may or may not help you repro it. But setting the flag on the page shuts off this error since it stops checking for this particular security scenario.