Javier,

I may add to Hilmars that if you add the pk to the view, a concurent view somewhere else will not know about the new pk and may use it also. You will not know when a new view - record is written to its table. Then you will have two new records (in view) with the same pk.

Agnes
>Hi all,
>
>When adding records with views I don't where is the best place to create the primary key, the view or the table.
>I generate the PK with a newId() function, and I don't know whether to put it on the default value of the view field or the default value of the table itself. I "have" to put the code in the table just in case I don't use the view; so I thought that if I inserted the newId() in the view I would end up creating twice the PK (and wasting PK), but I tested and it was not the case. So I don't really know what should I do from a "good practices" point of view.
>
>TIA,
>Javier.