>>i like using a primary key because it makes the update command straightforward.
>>you can define which records you wish to update in terms of the primary key.

>Right. I guess I wanted to point out though that it wasn't *needed* as you said, >depending on how you're updating. >If you use the command builder, then yes you need a PK, but not necessarily otherwise.

To clarify, a field does not have to be designated within the foxpro table builder as a "primary key". As long as the field uniquely identifies each record it can act as a primary key and allow one to narrow their UPDATEs and DELETEs to a single record via the WHERE clause.

Dave.