>I am doing some testing on moving my VFP tables to SQL Server, using the VFP Upsizing Wizard. So far, may VFP app has used free tables, so my first move has been to move the tables into a DBC.
>
>When I upsize the DBC to SQL Server 2005, the tables and indexes went over fine.
>
>Now, over in SQL Server 2005, I have learned about this wonderful Primary Key and Foreign Key deal. Very nice. However, these are not present initially, so I manually created them on a few tables just to see how they are used in SQL Server and in some of the .NET programming tools like LINQ.
>
>Now, I want to see if I can go ahead and set this up in my VFP DBC, so that when I upsize for real (one day when I am ready), that the PK and FK settings will push right over.
>
>So... The question is: Does VFP have REAL Primary Key and Foreign Key attributes, or not? It sure seems like all these years (in VFP) I have been thinking I was using PK's and FK's, but what I have really been using is INDEXES that we have been calling PK's and FK's.

Matt,
SQL Server also uses INDEXES to have PK and Foreign keys. So yes VFP has real PKs and FKs.