>In this scenario you have to create the PK in the view. I use views mostly for children tables, so I did not thought about this. I store the PK in a separate table, so I don't need GUIDs. If I create twice the PK (in the table and in the view), I thought I was wasting PKs; to my surprise it was not the case. I have to research deeper to know why didn't VFP created twice the PK. Besides, I was not really concerned about wasting PK, as with an integer type I get 4 billion PK (including negative integers).
The reason you are not wasting primary keys is that the code to create a primary key doesn't fire unless the field is empty.
