>>If you have a view based on a local table, and the local table has a Default
>>Value for the primary key, you need to make the Default Value for the view's
>>primary key field the same as the table's primary key, and make it updatable.
>>Otherwise, it tries to store Null (Blank?) there, and that violates the PK.
>Now, must I "provide" a value for the PK field if I add new recs to the view or
>will it "automatically" be assigned a value based on the Default value in the
>field validation of the original table the view is based on?

Yes, you must provide that value, unless I've been really stupid for the past couple of years (always a possibility :-) ).

<*rapidly typing in VFP window*>

Yes, I have been an idiot for the past couple of years -- or at least nearsighted. The way I've been working, that's the way I had to do it, because I've been using Table Buffering on parent and child tables, and to be able to wrap the updates in a transaction, I had to assign the value to the parent table directly, rather than do the update so I could get the child's foreign key. However, that didn't mean I had to do it all the time....