Probably something to do with my idiotic approach, but not sure. OK, playing around I realized that EVAL should be used instead of Bind, so that takes care of the extra field being passed back.
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.
This allows you to provide an event-handling method that performs a custom routine, such as configuring the Form View control for a specific mode or canceling the mode change, whenever this event occurs.
event is raised when an Update button within a Details View control is clicked, but before the update operation.
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.event when an Update button (a button with its Command Name property set to "Update") within the control is clicked, but after the Form View control updates the record.This allows you to provide an event-handling method that performs a custom routine, such as checking the results of an update operation, whenever this event occurs.2) Is so, when I cancel the edit (because I did the update myself), and change mode, the Form View returns to read only mode as inteneded (good so far).However, when I hit F5 (refresh), the Item Updating method is called again, and updates the database.It is generally used by control developers when extending the Form View class.