Hi!

I afrain there is no easy answer to this. However, I have found some weird behaviour of COM object instantiation from VFP with the same error, but this is for remote COM objects only, tried to run them from the same machine. Maybe ASP tries to use DCOM or something like that? What kind of COM object you have (EXE/Dll)? Did you ever registered it under MTS?

>Ever since I ran SP4, every single &*@#$(ing time I try to instantiate a new VFP COM object from an ASP page, I get a "Library not registered" error.
>The problem is that the library is registered. VFP can create it. VB can create it. The ASP page is the only one that cannot create it.
>Is there something I'm missing that I need to set?
>
>TIA