>We are calling a VFP COM component from ASP.NET and the VFP COM component happens to call another COM component (which is a .NET COM component)
>
>It works fine on the machine that everything is compiled on (iow, the developer machine) but once it's moved to a different box, it seems that the VFP component can't find the .NET COM component registration.
>
>We've registered the COM component manually and registered the typelib, etc. but this one is dogging us.
>

If a COM client is calling .NET, the .NET assembly must be installed in the GAC. You can do this with GACUTIL or by dragging the .NET assembly into the \WinNT\assembly directory.

HTH