Hi John,

I've just spotted the problem. The code sample I sent was being executed from within a sproc and that sproc was wrapped in a transaction. When I remove the...

Perfect. Thanks very much.

It doesn't matter which row is returned. If a case has two documents created on it in one day, I just need to know that a document was created on...

Sorry, I should have said that I'm working in SQL 2000 so I can't use OVER()

You're right, I could check the ROW_NUMBER() but I only actually need to know the...

Thanks for that. That's narrowed the returned dataset but we still have duplicates where rows with the same CREATIONDATE exist

CREATIONDATE | ...

Hi Graeme,

I've added that part in as an additional job to the replication process and it works perfectly.

Thanks,

James

Thanks for your help with this, guys. The solution was:

USE MyDB

PRINT 'Adding MYTABLE table to replication publication in ' + db_name() + '...'

--Add new article to publication

EXEC sp_addarticle @publication =...

Hi Graeme,

Thanks very much for that. I've only just returned to this project today and it works a treat.

I do however have a 'cannot drop the table 'XXXX' because...