>>Barbara -
>
>>On a related subject (speaking of relationships) I was reading a thread from several months ago where you explained how you used a view in a grid and included in your view the parent.contactid as well as the child.contactname. I didn't include those 'related' fields in my view, only the fields I wanted to display (and the primary keys of each table) in the view. If I understand your message, it sounds like I can avoid having to set relationships (i.e. for combo boxes, etc.) altogther by adding these additional fields to my view.
>>
>>Sylvia
>
>You can include any fields you want in a view, and sometimes it is very useful to have keys as well as 'visual' data. The only problem is that the more fields you have the longer the view takes to load. If the data set is small, this is not important.
>
>HTH
>Barbara

Thanks Barbara -

I knew I could include any fields I wanted; I just didn't see a reason to include fields I wasn't going to display (e.g. that key data) until I had read your earlier message where it looked like your were relying on the existence of the key field in the parent to relate to a description in one of your child fields. Anyway, I tried it and eliminated some of my 'set relationship to...' and it worked.

Sylvia