Right, who thought it was a good idea to insert into the dbo.Name table AFTER the user defined tables!

This is crazy given that a user defined table can have a trigger defined which expects, understandably, that a record in the primary dbo.Name already exists. I am pretty much lost for words, and feel like swearing.

Because that's not going to help matters, I just want to say that this has surely got to be one of the least brilliant things I have seen in a LONG time.

Because of this I am now going to have to spend quite a bit of time adding a workaround so that a CContact record inserts first into its core tables (of which dbo.Name is one of them) and only then insert into the user defined tables.

Honestly guys this is really poor.

Christian