http://en.wikipedia.org/wiki/Unique_keyFrom the entry: "Depending on its design, a table may have arbitrarily many unique keys but at most one primary key."
>>That comes from the DD. If you have the DD setup correctly (it's in the helpfile), it's done for you.
>>
>>Hank
>>
>The problem is, that it seems like I can not have the same table engaged in different relationships with different tables.
>
>I found that you can only have one VPMPrimary index, which I believe is critical for pick lists.
>
>In other words, I have a Manufacturers table. Another table is linked to it by Name field. I added a new MakeID field and wanted to link by this field from my other table. So, I set VPMPrimary on this new tag (MakeID). Now the old form produced an error.
>
>I resolved the error by making Name tag to be VPMPrimary, but does it mean I can not use the same table different field as a primary index?
>
>A bit confused on the functionality here.
