>>>>>I think I'm really confused about how a web page works with respect to control event.s
>>>>>
>>>>>I have a textbox on my page. I want to know when the user changes something, so I dbl-clicked the TextChanged event - which
>>>>>doesn't fire unless the Texbox tag has the attribute AutoPostBack = "true" in it. At least, this is what's happening in my page.
>>>>>
>>>>>This of course causes the entire page to be reloaded.
>>>>>
>>>>>This is really screwy. I gotta be doing something wrong.
>>>>
>>>>That's how it works - the event has to be handled on the server. You really don't want to have the TextChanged event cause a postback (certainly not on an internet connection)
>>>>
>>>>>What if I want to collect data from 3 different textboxes, THEN send it all to the server. But I want to know when any field was
>>>>>changed? I'm not interested in firing off to the server when the user types, I just wanna know that they did type.
>>>>
>>>>Assuming that you did know that they typed something what would you want to do about it? (genuine question)
>>>
>>>
>>>I have 3 fields on the page. There is also a Save button. When the user changes the text in a field, I want the button to become
>>>enabled. Even if it was already enabled, I would not want to push data back to the server that has not changed. So, to answer the
>>>question, I want to know that data has changed. I am trying to use the tetChanged event to store a mode as a session var so I know
>>>what happened.
>>>
>>>I'm wide open to suggestion.
>>
>>
>>Put the 3 fields and the button in an AJAX updatepanel. Any events you handle will only result in postbacks for the fields and the button.
>
>I don't think I understand. Postbacks are what I DON'T want, correct?

Some postbacks are required unless you want to write a lot of client side script. When postbacks are limited to only affecting a couple of controls, they can be almost transparent.