Pros and cons of editing related data in the datagrid versus separate form

  • Thread starter Thread starter Earl
  • Start date Start date
E

Earl

I'm looking for some insight into the best method of editing related data
being shown in the datagrid. I've had several tricky issues -- ultimately
resolved -- with editing data directly in the datagrid. David Sceppa shows a
method in ADO.Net using the currency manager where he forces the user to
click an Edit button to bring up the row in a separate form. Editing for
that particular row is then done on the form and saved, dropping you back
into your grid form. I'm not real excited about the idea of creating a bunch
more forms for all the datagrids in my current app, but it certainly would
resolve some problems editing data in this fashion. For those who have done
this using both techniques, any insight that you can share?
 
Earl,

When you use the datagrid than you have two problems.
Deleting a row and the edit without a button.
Because we are now talking about the edit, than when you have a button, you
can put in the method you use

BindingContext("The datagrid.datasource as is in your
code").EndCurrentEdit()

That makes it a lot easier for you and your user than the method you
describe.

Just my thought,

Cor
 
Hi Earl,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you need to know the advantages and
disadvantages of using a datagrid to manipulate data. If there is any
misunderstanding, please feel free to let me know.

Based on my experience, when you use datagrid, it is very convenient for us
to view all the data and modify them. However, we need to call
EndCurrentEdit before updating to put changes to data source as Cor
mentioned. Or we need to force the end use to move to another row after
modifying a cell.

If we use use a seperate form to modify data, we can update at the time we
need. But there will be a little bother for the user to open a new window
each time.

To me, I prefer to use datagrid directly.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Back
Top