Rowupdating oldvalues empty
The difference between your code and the code on MSDN is: - The MSDN code takes the new data from the edited row and updates the appropriate data in the To me, this is garbage, because it's so highly coupled to the order of your cells.
NET that is bound programatically in the Page_Load function.
I'll try to address your question, but I'm also going through some of the other problems here.
Without seeing your markup, it's hard for me to tell if you've created .
New Values are only available when binding the Grid View with the Data Source ID property.How are you binding the data columns from datasource, through the Bound Field or template fields with customized html ? | | - Mark | Empty Data Text="the cart is empty" On Page Index Changing="grid Cart_Page Index Changing" On Row Canceling Edit="grid Cart_Row Canceling Edit" On Row Deleting="grid Cart_Row Deleting" On Row Editing="grid Cart_Row Editing" On Row Updating="grid Cart_Row Updating" Hi Mark, Thanks for your response and the code you provided, so you're using a custom class collection without using any Data Source control, I think this should be the cause of the parameters collection in Row Updating event being empty. Anyway, you can also add the suggestion on the MSDN feedback center. (This posting is provided "AS IS", with no warranties, and confers no rights.) -------------------- | NNTP-Posting-Date: Mon, -0600 | From: Mark Olbert | Newsgroups: microsoft.public.dotnet.framework.aspnet | Subject: Re: Grid View: Empty Old Values, New Values | Date: Mon, -0800 | Organization: Olbert & Mc Hugh, LLC | Reply-To: ma**@| Message-ID: | X-Newsreader: Forte Agent 3.1/32.783 | MIME-Version: 1.0 | Content-Type: text/plain; charset=us-ascii | Content-Transfer-Encoding: 7bit | Lines: 11 | X-Trace: sv3-U9n K6Tome E9bhjk We Xcn08z AR1r LXufi10Yw Ngyd0i3SWg Cu z Pj D1xg6GVJGAb K7Dnh2WO b Vwt Og T! Also, if convenient, would you post some detailed code snippet of your page and the code behind on this? All the parameters are actually associated to the Parameters declared in Data Source control (the select and update statement in Data Source control), also we can find some parameter name related attribute such as Old Values Parameter Format String="original_" So when we do not using Data Source control, there is no info for populating named parameters .... Also, I think it'll still require us to use Data Source Control when we need to Updating event to contains Parameters collection, however, it may become more user friendly if there're some additional functions on the Data Bound control which can help extract bound values from each row /column... ha AJ9Znc P8Ei3q L2 n GKN1K6B5U57An5w PDTl Bf TR hgoc D5IBPrxek8Ok Q6ARdran47 nw== | X-Complaints-To: ab***@| X-DMCA-Notifications: X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers | X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly | X-Postfilter: 1.3.32 | Path: TK2MSFTNGXA02gbl! From some googling it appears that, at least in the release candidate for NET2 this was a known bug; only binding to Data Sources lets those dictionaries be populated. | | From some googling it appears that, at least in the release candidate for NET2 this was a known bug; only binding to Data Sources | lets those dictionaries be populated. 2) I think it's weird that the "value" capability is tied to the parameters collection. That way it'd work with both types of data binding. I would like to confirm that this is a problem with the released version of NET2, so I can stop beating my head against the wall trying to get the Grid View to work "as advertised". As for the Grid View control doesn't correctly populate the Old Values or New Values parameters collection when performing udpdate operation, I think it is likely caused by some certain setting in the Grid View control... | | I would like to confirm that this is a problem with the released version of NET2, so I can stop beating my head against the wall | trying to get the Grid View to work "as advertised". - Mark Thanks for your followup Mark, Frankly speeking, I do agree with you that this is a big limitation since I haven't noticed this before until you mentioned this...