Hi Trent,

Thanks for the inside, I will start working on this form and then if I get stuck will ask for help.  My main concern was about the possible mis-used of the BO relationship, but if this can be handle by SF, then all I need to focus is on the BO state to enable/disable buttons based on the parent BO state.

Edhy Rijo

Sure, it is possible.  We have some forms in our medical app that allow users to view and deal with many child tables.  This is somewhat of a difficult question to answer over the forum as this can get really deep and somewhat philisophical on form design.  But we have had great success with some of our interfaces.  We actually intend to hit on this in the next training class...form design and user presentation is something that we all deal with and we are going to share some of our experience in the class.

I really didn't know how to give you a quick answer here.  This is something that generally requires some conversation to work through the entire process.

Hi guys,

I have 4 basic tables which are related and I would like to show as much info as possible in a single form like this:

The tables are:

• Insured: Main parent table
• Policy: related to Insured
• Vehicle: related to Policy
• Driver: related to Vehicle

What I am trying to do with the above form layout is to have the Insured data upfront and then allow the user to enter any detail data via the ListView at the bottom.  I am not sure if the above relations can be handle by SF on the same form in order to show all related data to its parent as well as to update the FK fields in the child BOs?

I would appreciate any suggestion/indication for the above form layout.  At this point I am exploring all new things I can do in .NET.

Thanks!

Edhy Rijo