Javelin- I prefer to use the Form View Command Event Args to read in the commands.
I've never tried it with my Sql, but I'm assuming implementation is the same since it's outside the data layer. Raise Bubble Event(Object source, Event Args args) 56 System.
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.
Again, formview is trying to pass these parameters So given that, I have defined the following even handler for a simple form view: (not sure if this is the way to proceed given the above, but...) protected void Form View1_Item Updating(object sender, Form View Update Event Args e) My questions are as follows: 1) Is this the right approach?
you could place whatever data logic you need to access your database, pass update commands, etc. NET 2.0, when used through manual databinding just require yopu top handle certain events, and they inform it this way. Handle Event(Event Args e, Boolean causes Validation, String validation Group) 545 System.
AFAIK, Item Updating is an event that fires just prior to whatever you have specified on the data source object as the Update Method. Basically, all you need to do is to attach a handler method for Item Updating event, and that's it. NET MVP Since I haven't had any success manually updating this formview, I thought I'd repost on another route I'm trying.
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.
Herpes verdict in Portland: Woman wins 900, 000 after getting.
If you're manually pushing your data into the Form View, then you probably don't have that event. To recap, I am manually binding to a datasource using the My SQL .
NET connector, and I've been able to run action queries on this database when directly coding them. Handle Update(String command Arg, Boolean causes Validation) 972 System.
protected void Form View1_Item Command(object sender, Form View Command Event Args e) Odd code...
was using it for an example in another thread, but same concept...
On your form view, just associate your Update, Edit, Cancel, etc buttons with similar Command Name parameters: Like so...