>Everytime I encounter a situation which requires Parent/Child relationships I toy with the idea of using a grid and allow the user to view and maintain. Simple relationships I find somewhat doable but when it becomes more complicated with picklists and various other controls in each of the columns it seems to become a nightmare.
>
>I generally end up just allowing the user to access the child through an entirely new form using a filter or something. It works fine and is infinitely less complicated.

What you are doing IS less complicated and IMO a "better" practice. I strongly discourage users from insisting on using a grid as an editing tool. Particularly when it is displaying a child table. A grid can be effectively used as a way of selecting records to be edited in some other manner besides entering and editing directly in the grid control. This is one reason I stopped answering questions about the wizard generated nav buttons.

>
>I hear of others that seem to just pop the controls into each column of the grid as simply as putting them on a form and move on. No problem.
>
>Am I missing something.

No. Chances are those people are not fully aware of the effect it would have on their data if you take the same code and let 50 users start whacking it at the same time.