I'm new to VB .NET programming and I'm stuck with this problem for the last 3 days. Any help is greatly appreciated.

I have two tables Master and Child. The tables are in a one to many relationship. I have a form which I should use to collect information for both the tables and also save the data.

The master table is set up as a details view and is linked to a binding navigator. I want to set up the child table also as a details view with its own binding navigator. I'm not sure how to do this. When I drag the child table onto the form as details view I cannot see any updates. But if I use the child table as datagridview then I'm able to insert, update and view the data without any problems. I cannot use a datagrid view due to the nature of data in the child table.

All the examples that I have seen uses the datagridview as the child for one to many relationships.Could someone please point me to an example or provide a direction to resolve this issue

Hi Ignatius,

You said: I want to set up the child table also as a details view with its own binding navigator.

Based on my understanding, the root issue is that when you move to one record of the head table, there are several records in detail table related to header table, but you can only see the first record in the details view of the detail table.

To have the user be able to select a record of the detail table, besides adding the details view of the header table and the detail table, we can add a DataGridView view of the detail table to the form. Then we are able to select one row in that DataGridView to select a record of the detail table.

If you would not like to add a DataGridView to the form, but need to add an own navigator bar to the form. We can add a BindingNavigator control to the form and set its BindingSource property to the BindingSource of the detail table(detailsBindingSource). Then we can use this navigator to select a record of the detail table. You can get more about how to use BindingNavigator control from: http://msdn.microsoft.com/en-us/library/system.windows.forms.bindingnavigator.aspx

By the way, we can always save the data via the Save button of the head navigator to save the data. So it is unnecessary to add a new save button.

Let me know if this helps or not.
Aland Li

---

Please mark the replies as answers if they help and unmark if they don't. This can be beneficial to other community members reading the thread.

Hi Ignatius,

You said: I want to set up the child table also as a details view with its own binding navigator.

Based on my understanding, the root issue is that when you move to one record of the head table, there are several records in detail table related to header table, but you can only see the first record in the details view of the detail table.

To have the user be able to select a record of the detail table, besides adding the details view of the header table and the detail table, we can add a DataGridView view of the detail table to the form. Then we are able to select one row in that DataGridView to select a record of the detail table.

If you would not like to add a DataGridView to the form, but need to add an own navigator bar to the form. We can add a BindingNavigator control to the form and set its BindingSource property to the BindingSource of the detail table(detailsBindingSource). Then we can use this navigator to select a record of the detail table. You can get more about how to use BindingNavigator control from: http://msdn.microsoft.com/en-us/library/system.windows.forms.bindingnavigator.aspx

By the way, we can always save the data via the Save button of the head navigator to save the data. So it is unnecessary to add a new save button.

Let me know if this helps or not.
Aland Li

---

Please mark the replies as answers if they help and unmark if they don't. This can be beneficial to other community members reading the thread.