[Updated] I think what we are both saying is that if no one has subscribed to the event (i.e., no one is listening for it), there's no point in raising it.
When it starts to performing this task, the Mode Changing event is raised (to indicate that it's in progress) (optionally do something here).
Once that task is completed, it raises the Mode Changed event (to indicate that it's done) (optionally do something here). How could you consume the events if they don't get raised.
I need to do a custom update for a form view (I think/know), as some of the parameters that are required for updating values should not be updated by the users, such as userid of the person performing the action which is passed back to the database for auditing purposes.
Additionally, there are some fields, such as Last Updated By, Last Updated Date that need to be seen, but not edited.
Here, they can check if the have filled out everything correct.
If not, they must be able to change the form, so the form must be changed to edit mode. 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.The stored procedure on the backend takes care of this, and these are not parameters for the Update method.The Form View by default is trying to pass all these values back to the database.Lasty, the select query of the object datasource is a stored procedure that performs several joins based on PF/FK relationships to bring back more meaningful information than just a FK, so some columns are just the joined value, and can not be updated directly.