>The standard solution I've read here and other places has been working well for me, tho' I resisted it for a long time. Use grids for displaying info and use controls outside of the grid for actual editing.

This definitely makes things easier, I can imagine. However, if the grid only has a few fields on it, it's just more user-friendly, IMO, to allow editing directly on the grid. For example, in my current project, the main user action on the gridded table will be to check checkboxes. It's so much easier for the user just to be able to check the boxes on the grid than check the right grid row, then go up to the input area.

However, I'm pretty new to grids, so I may end up eating my words. :)

One problem I had today was deleting records from the grid. I won't use the built-in method of clicking on a tiny little column, so I have a Delete button. My problem is determining whether a grid row has been selected, i.e. has a mark in the leftmost column. I've resorted to setting a record number property in the grid's AfterRowColChange (when a row has been selected), and having the form clear that property when another record is accessed (ugly!!). Do you have a better suggestion? In particular, how do you decide what to fill in your child input area with when a parent record is first displayed?