In this respect, Joe and I are in absolute agreement.

And how would you start the job from TSQL on the remote server?

By executing sp_startjob using the 4 part name.

You are correct, Phil. That would be less confusing.

The key is that it thinks the user account is Null. Tell the user to reboot their machine. In most cases I have encountered this resolves the issue. If not,...

Sergiy is almost correct. Null does not equal 0 and Null does not not equal 0. That's why we use "Is Null" and "Is Not Null" instead of "= Null"...

CTE = Common Table Expression.

There is no equivalent functionality in SQL 2000. If you post the actual view statements, maybe we can help.

Be aware that the Use statement will only apply to the dynamic query being run.

Look up "XML bulk load [SQL Server]" in Books online. Bulk load the XML document into a table and then use sp_XML_preparedocument.

Don't use "getdate() - 30". Use the DateAdd() function.

Post your code where you call the procedure. You're not calling it right.

No. You know how to set up a view locally where the user has permission to the view but not the table(s) right? Do that and then on the remote...

Use the 4 part name:  [Server].[Database].[Owner].[Procedure]

Exec MSDB4.MyDatabase.dbo.MyProcedure

You seem to be taking this very personal. I'm not sure what that's about, but I'm sure it's nothing that a few hours on a couch can't resolve.

Yes, we use...

I've never tried that approach though i have done the opposite (with procedures, not triggers) that would only run if the calling user was logged in with my SQL account...