Re: GridView RowEditing Requery question

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for your followup Matt,

Sure, if the dataset is quite large, you do need to consider the memory
pressure it may bring to your server machine. Actually, what I wonder is
whether you'll need to frequently load different (can not share) instances
of such dataset from backend database. Also, if the application is serving
concurrent client users, can such large dataset shared by users or each use
will have an individual copy, if each user will own a specific copy, that
make the memory pressure further critical. For such scenario, I would
suggest you consider some other kind of data editing/updating in your
ASP.NET page. For example, instead of using GridView to do both data
displaying and edting, you can use GridView to display data only, it can
display all the data records in rows, then, for each record, when user
click edit button in GridView, you can popup/display another separate
FormView or DetailsView for editing the selected record, since this record
can be located through its primary key(rather than ItemIndex in GridView),
you can avoid the inconsistency issue in earlier case. How do you think?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.


.

Quantcast