>Well, to get it to process remotely, the remote server has to have the data. The only way to get the data there is to pass it (usually via a string like XML) or let the server go fetch it. Splitting data that relies on each other across servers is generally a bad idea, IMO. And this is a perfect example of why.

What I finally ended up doing is to dump the cursor on disk into that main server. Then, I can SQLExec() having all tables on disk.