Kevin,

Thank you for the suggestion. The combo is a good idea and it is what I've usually done in VFP for FK values a user can edit. I realize I wasn't quite clear in my question and example: I'm wondering how to simply *display* a lookup value in a navigation grid (not edit it).

In maintenance forms in VFP, I've tended to avoid doing edits in navigation grids. I've usually set the grid or "List" page to readonly and required editing to be done on a Detail ("Property") page. I think you are right that once the user clicks on the Detail page to edit a record, the combo box works great at that point.

Maybe a combo box in the navigation grid would still work best even if it is readonly? It seems that filling the grid with a multi-table view causes problems when you try to edit it in the Details page. Maybe setting up a DataRelation to show the looked up value is better.

Any further thoughts would be appreciated.

Larry


>Actually I use a combo box in most of these situations because it binds to a foreign key pointer, but displays a user-friendly description. Is this an option in your UI?
>