Damon gives just one example of a poisoned dagger in the game of Sharepoint Development: The Item Event Receiver.I’m usually disappointed when writers employ oft-overused metaphors to describe a situation.Can you explain this and let me know how I can get around it?Thanks again Andrew OK, I have to check for an exception in here too.
Update() Ryan posted a solution to this issue, using a custom event handler that disables the events upon request.With the Form View (or any of the Data Views), I normally use a Data Source to move data from some data store and into/out of the view.However, the Form View (and the rest of the Data Views) will work just as well with any collection of objects: Lists, Arrays, Array Lists, or whatever collection you want to make available to the user for display and update.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.