Linda,

>I figured out a few things but still can't get everything to work right. I have code in the Text_Changed event, which is triggering a post back (because the user has to press ENTER to get it to fire) with no place to update my session dataset variables. Consequently, I get an extra trip to the back end before saving my data set variables and lose everything that was just entered. I disabled the submit for all but one of my buttons except for a save button, hoping to route all the submits through there so I could update the session variables in the click event of the button but that apparently fires after the submit as well. Then I tried saving the session variables in the unload of that button, hoping the dataset variables would save right before posting but still no luck. Next I plan to abandon the Text_Changed event and put all the code I want either in the page load or in that button click.
>Basically, my problem is that the users want the responsiveness of the desktop environment but management wants everything on the web so they can get to the data (users are widely distributed) and, probably, keep the cost of the user computers down. I lost the fight trying to convince them to stick with Windows Forms for this application, at least for now.

If you want to execute some code immediately when the user types a character, you may want to use JavaScript because it doesn't require a round trip to the server (and thus no post back).

>I haven't really looked at Silverlight. What would that gain me in this process?

Silverlight allows you to build applications that are far more like Windows Forms applications--the code runs on the client machine by means of a Silverlight browser plug-in. This works great in scenarios where all your users have either Windows or Mac desktop machines. It doesn't work well when writing for smart phones or tablets.

Best Regards,