I don’t mean that it’s largest and most luxurious application every written, but rather that you may be cruising headlong into a nasty rendezvous with an iceberg that could deal a severe blow to your project.

We may never know about all of the dangers lurking out there, but today we’re going to cover at least one danger you may encounter while writing event receivers – an annoying issue with the Item Updating and Item Updated events firing twice.

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.

Is there a better or more appropriate technique I could use?

Thanks Andrew Hello Andrew, Is the redirect here means redirect the current page to another page/url? Client Script to dynamically regisgter a clientscript to do the redirection at client-side.

Do I have to call the Change Mode() method in the Mode Changing event handler? I can see the mode in the process of changing, because my Mode Changing handler gets called, but then the Mode Changed handler never gets called.

NET Data Views are powerful tools when coupled with a Data Source.

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.

You won't get automatic generation of the Data View's templates and you'll have to write a little code, but from the user's point of view, everything works as if your Data View was tied to a Data Source.

So here's how to use a Form View to display—and let the user update -- any collection of objects.