"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:etvoroNaEHA.1652@TK2MSFTNGP09.phx.gbl...
> Bruce,
> presumably you are using merge, and the insert failure is the insertion of
a
> row into MSmerge_tombstone.
> I don't know how these rows have managed to be entered without having a
GUID
> as this is a default value. Either they were entered with an explicit null
> or they were already there.
> To remove them, it depends on if they exist on other servers or not.
> The easiest way is to use ALTER TABLE DISABLE TRIGGER deletetriggername
then
> remove the rows then reenable the trigger. Obviously you must ensure there
> are no other changes going on while you do this type of manipulation.
> HTH,
> Paul Ibison
>
>

"Bruce Baker" <bruceb@ardex.com.au> wrote in message
news:%23yyb9VNaEHA.4048@TK2MSFTNGP10.phx.gbl...
> Hi
>
> I have a subscription which has a table and some rows which I cannot
> delete - they don't have a rowguid value set for them - when I try and
> delete I get a message about 'cannot insert a null value into column
'guid'.
>
> How do I tidy tihss up ?
>
> thanks
>
>