>I'm sure I will learn and adopt many new techniques as I crawl out of the newbie stage :) I just thought that this would be a trivial task for a grid. In FPW or FPD I could easily construct a browse that contained fields from child tables. I know the grid is far more advanced that a browse - I just thought an invoice detail grid that displays a part's description from a products table would be child's play. Then again, I haven't crawled to the level of VFP child yet :)

Some VFP pro's argue against doing data entry in a grid at all.

I use SPT to handle your kind of situation. The product description is included in the cursor of line items, but only the product PK is physically in the table.

SQL (views/SPT whatever) lets you easily present the data they way the customer/user wants it. I don't bother with direct table access for new systems and haven't for years.

>
>>As long as you're learning about VFP look at views instead of tables. After learning about those perhaps you'll change your mind and use them in your forms instead of tables. I'm still working with VFP7 (getting soon to VFP9) so there's a thing I know nothing about and it's called a cursor adapter. You should study that too. It looks very interesting.
>>