>
>Chris,
>
>The same thing happened to me this week. I am on NT4 Server with SP3, and IIS3.
>
>I created a DLL in VFP5 and could access it's properties and methods from Excel 97, VB5, VFP3, and VFP5 with the CREATEOBJECT() command. However, I kept getting an error message with the exact same code in my Active Server Page.
>
>Fortunately, the NT Server PC that I had the ASP errors appear on was the development PC. We have another NT Server PC that we use as our actual web server. I moved the DLL over to the Web server, registered it, and my ASP worked great.
>
>Both PCs are NT4 Server with SP3 but there has to be a problem with my PC. We are going to try to re-install the SP3 to see if this helps.
>
>This one really stumped me for a few days. Hope this helps.
>
>Jerryt

Thanks for your kind advise. I ever thought this is the reason. But I still failed after I re-install another NT4 server! I think I must do this again to see if I have made something wrong.

And, another question: How do you "update" the DLL when it's already in memory? For example, I have a DLL, and called by a browser, and works fine. But I update it for some purpose, then build it in VFP, and VFP told me that I cannot update that DLL file(file access denied). So I could just give that DLL another different filename, but internally same class hierarcy. I know that MTS 2.0 could "shutdown" the DLL if you let it manage your DLL. But how can I achieve the effect before I can get MTS2? This problem also happened in VB5 or any other client tool.


Chris Lee