Hi Martin,
>
>>It was the presence of CHR(13) in the XML string.
>
>Devil's in the details. ;-)

Isn't it always in this business?< g > It just goes to show that nobody has all the answers.

>>>The second one is to put your DLL into COM+. Then the only thing you have to do is stop that single package, install the new version, and that's all.
>>>
>>Yeah, that's the next item on the agenda, getting it into COM+ and passing the string that way. This thing is more or less a research project that I'm using how to do things like this. Haven't messed with COM+ yet either, so youi might say that I'm behind the curve there too.
>
>Well, I think you really have to take a look at it. It is far more easier that it seems (at least for simple things), and it will save you a lot of troubles. I wrote an article with very simple example and a step-by-step guide on how to put a DLL on COM+ you can read on:
>http://www.levelextreme.com/Magazine/July2002/Page22.asp
>
>I'll be incredibly happy if something I wrote help you at least a bit, after all this years of taking advantage of your knowledge and guidance, George.

Be assured that I'll be looking at the article tomorrow morning. In reality, at lot of what I've picked up on over the years has come from other folks' posts.

>>BTW, thanks for the nice remarks in another thread about the WSH article.
>
>Please, I'm just stating the truth. I received incredibly usful advice from you and Ed.

Well, if it weren't for Ed, I'd have never even gotten into the WSH. If it weren't for Ed, there wouldn't have been an article on the regular expression parser. Far more credit should go to him than me.

Best,