>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?
>

One thing comes to mind - did you deploy and register the new SP4 runtime modules on the server? The runtime did change between SP3 and SP4, so perhaps it's the runtiem library at issue rather than the COM object itself. This would explain why it runs OK under VFP - the SP4 stuff is obviously present on the developer's machine, but maybe the server needs the new runtime components installed via Setup Wizard or the MSM which ships with VSI 1.1 currently.

>>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