I've had a response from Ken Cox (MVP) -this might be the problem (I shall
go thru)....
http://authors.aspalliance.com/kenc/faq6.aspx
"Mark Broadbent" <> wrote in message
news:eulJvwJ$...
>I initially posted a problem in the aspnet.webcontrols and have now found
>why the problem existed. Just thought I'd post this to see if this was
>perhaps a known issue.
>
> Scenario: I have a simple webform project that was created on one machine
> and transported to my work machine. The form has two buttons Edit and Add
> which do not cause validation. When either of them are clicked they fire
> their respective events and cause textboxes (and the Save and Cancel
> buttons) to come into view. The form has RequiredFieldValidators for the
> textboxes -which display when the Save button is clicked.
>
> Error: Both machines have the same uplevel browser (ie6). On machine 1
> everything works fine. On machine 2, when the Edit or Add buttons are
> clicked they do not fire their events (if I set them to causes validation
> they do cause the FieldValidators to work ...but still don't fire their
> events). I noticed that I can get the events to fire if I set the
> FieldValidators to EnableClientScript = false
>
> Points to note here.
> 1. My code works fine on machine 1 properly
> 2. Both machines have the same uplevel browser
> 3. Since both buttons are non validating, they should be uneffected by the
> Validator controls anyway.
> 4. This is really p**s poor and has cost me an entire mornings work.
> 5. When problems like this occur you start to question the whole question
> of programming for uplevel browsers if you can't rely on the code
> executing correctly
>
> Has anyone else come across this or similar problems.
>
> Br,
>
> Mark.
>