Hi all:

I am trying to define a new field which can be a primary key in a VFP database table.

However, I got to the point of confusion with SQL Server primary keys. In SQL Server, the primary key is a clustered index by default. By clustered primary key, if I understand it right, the data is physically sorted on the primary key; i.e., the index definition is "clustered" in the data. If I insert a new record in SQL Server where the primary key ends up in the middle of the table, the rest of the records will be moved physically. Fill factors and SQL Server's data management may help in minimizing these movement operations by allocating extra space in advance for new data.

In VFP (esp. VFP9), is the primary key also used to physically sort the table? I.e., is it a "clustered" index? I tried to look for such information in VFP9's help but cannot find it. In my changes, I do not want it to behave like a clustered index where inserting a record will move the rest of the data unnecessarily. If the VFP primary key behaves as such, I would resort to using the new field on a candidate key instead.

Any information will be very helpful.

Thank you.