>In VB every record created can have an automatically incremented primary key, when using Access data files.
>

Yeah, the counter field type is nice in Access.

>Can VFP table be structured to do the same automatically? If not, what do you suggest would be the most efficient and valid way of creating a value to be used as a unique primary key in a multi-user environment?

We don't have a field type that takes care of this, but most of us use a strategy that acheives the same effect: use the default value property for an integer field to call a stored procedure that looks up the next available id in a second table that stores only table names and ids.

For an example, look at the TasTrade sample that ships with VFP.