Hi, George!

>I've been banging my head against a wall for long enough. Being "Internet challenged" (I deal mostly with desktop appications), I thought I'd turn to the one place that I could count on to answer something that I haven't been able to figure out. Here's the scenario...
>
>Using IIS 5.0, I've been trying to pass a valid XML string to an ASP page (I told you about the TLAs < g >), as a parameter, to my local machine's ASP page without success. The ASP page, using VBScript, creates an instance of a VFP DLL, which it's supposed to pass the XML string to for processing.
>
>I've inserted output to confirm the status of the operation, and all seems fine. I created a function in the DLL to return a string, and it works perfectly. The parameter seems to have been passed successfully from the indications displayed by the ASP page. However, the MTDLL, otherwise seems to not process the XML string. Any code inserted to display it or its length fails.

I assume that you aren't trying to display something from *within* the DLL. You can put any UI on a DLL, but I think you already know that? Have you tried to log that to a .txt, for example, to see what's arriving. Debugging DLLs is hard, and that's one of the things I do often. I basically use a TXT as my "debugout".

>The question is: Can you pass an XML string to an ASP and have a VFP DLL process it?

Yes you can. There must be some tiny detail there.

>There's a side issue here too. Despite all my attempts to make sure that the object reference gets released, it doesn't. I've got to re-boot to re-build the DLL. Anyone have a clue about this?

The DLL is cached inside IIS. You have two ways:

The hard one is to open a CMD window ans issue IISRESET. That woudl reset the whole IIS -not very elegant for a production server.

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.

Hope this helps,