It depends on the application, or rather, how the users work with the data.

If a full order is accessed at one time, I would have the data that
corresponds to that order open in two editable "grids" or "regions" (could be
a set of panel controls). The user can edit at will. In order for this to
work, the database must used derived keys, as the user friendly order number
could be edited.

If the user only edits lines, have them click the order to get the lines. In
this case, the relationship is not really of issue with the application.

The Update process can be done via Update() on the DataAdapter, but make
sure you check for concurrency errors.


---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"IMRAN SAROIA" wrote:

> Hi!
>
> Please advise what is the best practice for modifying and updating
> the many sides of relations. E.g., For orders , order detail side.
>
> I used to following approaches:
>
> 1) Gettting the data and bouding to data grid at run time programmatically.
> 2) Directly bounding to Grid
> 3) Taking entry in dynamically generated text boxes.
> 4) Getting the data in text boxes and then filling the Grid with that data.
>
> Thanks
>
>
>

Hi!

Please advise what is the best practice for modifying and updating
the many sides of relations. E.g., For orders , order detail side.

I used to following approaches:

1) Gettting the data and bouding to data grid at run time programmatically.
2) Directly bounding to Grid
3) Taking entry in dynamically generated text boxes.
4) Getting the data in text boxes and then filling the Grid with that data.

Thanks