It is my understanding that having executed this stored proc from within .Net code, you get back a dataset that has multiple tables - each with their own structure. All...

Forgot to mention, there is no need to publish anything other than what you are doing now. Just the table you need and the triggers flag should get the job...

Using MSDE should make no difference. As far as I know triggers are fully implemented in this version of SQL Server

Couldn't see your attachment so can't make any suggestions about...

Just checking if you have installed the necessary hotfix at all subscribers to take advantage of the compensate_for_changes proptery?

The article at http://support.microsoft.com/kb/828637 talks about this in the remarks.

It might be...

Here is a conceptual look at one

All you need to do is fill in the bits. I've borrowed some of the stuff Dave talked about in his article and just...

A couple of possibilities that may or may not be valid.

You are out of disk space on the drive where your tempDB resides

You have restricted the growth of the tempDB...

If you look at the properties of the publication, then look a the articles tab.

Select the article that the trigger is associated with and click the button with the ellipses...

Yes, good point.

Take the two pronged approach and use a RAISERROR inside the stored proc too. This way you get messages as they happen but also an easily searchable set...

Oops, slight error in my example - lets try again

EXEC DebugSP @message, Paramlist

-- Statement block runs here

EXEC DebugSP @message, Paramlist

I like the concept but I generally take a slightly different approach.

Use of a logging table that is populated by a single stored procedure that takes in the descriptions and...