Information générale
Catégorie:
Visual ProMatrix
Versions des environnements
Network:
Windows 2003 Server
Hi Naomi,
VPM follows standard RI theory. There can be many candidate keys (unique value per record); but only one primary key, which functionally is also a candidate key, but is the one and only key used for relations among tables. There is nothing you can't do following that conceptual scheme that you would do with movable primary keys. Just follow standard RI theory, and VPM will work with you.
Hank
>>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.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement