Can you explain this and let me know how I can get around it?
event is raised when a Form View control attempts to switch between edit, insert, and read-only mode, but after the mode actually changes.NET 2.0 most of the examples and tutorials deal with setting the Data Source ID, which buys you a lot of automation that you may not even appreciate unless you’ve done this the old fashioned way.In this example, we’ll go through a fully featured Grid View with editing, deleting, selecting, sorting, and paging functionality that is manually bound and identify the limitations and some of the workarounds. Sql Data Source, Object Data Source, Linq Data Source, etc) specified in a Data Source ID, the Grid View can automate many functions because, through the data source control, the Grid View on its own can perform the following operations: When you manually bind data to a Grid View, the Grid View itself cannot perform these operations, so they must be implemented in your code.We can register the scritp in the certain update button's update server event handler.Since the client-side code will be executed after the page is rendering to client, all the server-side code will be executed as normal. And for client-side redirection, you can use window.= "new url" to do the work. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. I'm not sure this will work for me as I may wish to use Server. I have discovered a more alarming problem with the Server-side redirect however: The exception thrown in the Object Data Source Inserted event does not stop the redirect in the Form View Item Inserted event. protected void ods Account_Inserted(object sender, Object Data Source Status Event Args e) // this still runs protected void fv Account_Item Inserted(object sender, Form View Inserted Event Args e) I find this very odd.Is there a better or more appropriate technique I could use?