Hi Ken and Lynn

Thank you both for your responses. I'm kicking myself now over the answer, I can see clearly what you are doing with both of these methods, for...

Now it may just be due to the way that the companies I've work for work, and the way that I do it, but in the context of the post...

For the majority of users I'll reuse the AD groups, which are setup for departments/roles, as I deal with both sides of the system and when I make a user...

For Kerberos and SPN to work, I'd need to change the SQL server from Local System to a domain account wouldn't I?

Cheers for that, I am the network admin, so I'll have to add it as a job for another day, but I've looked at the MS documentation on it, and...

For anyone interested I've now resolved this problem. The issue is due to there being no unique index on the target table, as soon as I created an index on...

Guess what...

Still no luck, same error. I have noticed that although we are SQL 2000 SP4, 2005 is still at original RTM status, I don't know if SP2 may sort...

Here is the info.......

Server: SAGE (server collation: Latin1_General_BIN)

SQL: 2000 32bit

Database: cleaningnet

Table: ImportTimStock

Table Collation: SQL_Latin1_General_CP1_CI_AI

Server: chersql01 (server collation: Latin1_General_CI_AS)

SQL: 2005 32bit

Database: [CleaningNet Interim]

Table: ProductsWaitingApproval

Table Collation: Latin1_General_CI_AS

Table: tmCleaningnet

Table Collation: Latin1_General_CI_AS

Chris

Nope....

UPDATE i SET catalogue_number = a.nwCode

--SELECT i.product COLLATE Latin1_General_CI_AS, a.sku COLLATE Latin1_General_CI_AS

FROM [sage].cleaningnet.dbo.ImportTimStock i

INNER JOIN ProductsWaitingApproval a

ON a.sku = i.product COLLATE Latin1_General_CI_AS

INNER JOIN [tmCleaningNet].dbo.products b ...

Chris

I've tried both, the SELECT statement worked, needed a few alterations on the columns and collate placements, however unfortuantly, the UPDATE causes the same error using this code

UPDATE i SET...