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

This is actually all running just on my machine right now, but thanks for the reminder.

I figured out the problem - MSKB#Q274038. The problem was registry security.

I had to add an Everyone entry with Read access to the HKEY_CLASSES_ROOT window using RegEdt32. The KB article above says that you should add this to the components that are failing, but I had to do it all before it would work.
On my local machine, the Everyone access doesn't bother me, but when this gets moved to the server it will. Guess I'll burn that bridge when I get to it :)