Stephen,

As primary keys, iId is fine, you seldom need to have multiple primary keys in the same view. As foreign keys, iCustId and iInvId are OK and are unique for view fields.

HTH

Rex

>I think that you are corect to unique your keys. IID, will look liek IID_A, _B, _C in your joins, but iCustID vs iInvID will never be confused.
>
>If you use views keep them separate! If you don't use views, keep them separate!
>
>__Stephen
>
>

---

>
>>Hi everyone,
>>
>>We are new to the framework and have a question. We are now in the process of building our tables. Does the unique ID of the table have to be IID? I noticed most of the examples and things that we looked at in class referred to it as either IID or CID. Can we name it something else other than that? For example, we have a table called Product. Could we call it IProductID instead?
>>
>>Thanks,
>>
>>Brian