More than likely it's a permissions issue. When you run it from VFP you're, no doubt, running it with Administrator or similar permissions, but, IIS users are anonymous and have far less rights.
>I have created a dll call makeXml.dll with VFP. The makeXml.dll instanciates another non VFP dll called CiscoUrlProxy.dll. MakeXml.dll retrieves data from a web page, formats the data in XML format, and assigns the string to a property.
>When I run the code in VFP it works just fine. However, when I call makeXml.dll from the ASP page it does not work property. The CiscoUrlProxy.dll that is called within the makeXml.dll captures web content to a string. I put an IF statement in the code that returns the string "There is no data" if the return string from CiscoUrlProxy.dll is blank. As I said earlier, if I run it within VFP it works fine, but if I run it from the ASP page it returns the string "There is no data". This suggests that CiscoUrlProxy.dll within my makeXml.dll is not being called correctly if makeXml.dll is called from ASP. Any ideas?