Hi

Thanks for your help, but it appears that even with the scripting error message the stored procedure is actually working as expected.

A cause for concern though.

Here's some sample XML:

<root><row orderid='178661' cargoready='2010/11/20' estpallets='1' estweight='2' estvolume='3' updguid='WUaJK1_FTkmu29vJk361_A' companyid='7' userid='2'/><row orderid='190430' cargoready='' estpallets='3' estweight='2' estvolume='1' updguid='WUaJK1_FTkmu29vJk361_A' companyid='7' userid='2'/></root>

It doesn't make any difference, I've tried setting the compatibility level to 90 and 100 and the problem is still there

Hi

It's a SQL server 2008 database, compatibility level = 80

Thanks

I'd just like to say I inherited this database, I didn't design it. Until I get to the point where I can migrate the data I have to work with...

Thanks

Attached scripts for the 2 triggers and the tables they affect.

My code is working - but the table has 2 triggers on it which have to be disabled befoe my script will work with. I therefore modified my script to...

As it turned out the table being updated has got a couple of triggers on it (it's a legacy database so I am still finding things like this hidden away).

The...