>Hi,
>
>We've developed a very simple COM Server DLL using Visual FoxPro 6 SP5.
>
>The DLL has been built as a Single Threaded COM Server.
>
>It works fine on both Windows NT and Windows 2000 on our test PCs. We install and register the DLL using a WISE script, and it is called from an ASP script.
>
>However, we tried installing it on one of our clients servers today. He is running NT Server 4 with Service Pack 5 installed. The DLL appears to be registered, but calling it from our ASP script gives a message that the object is not registered.
>
>We have tried manually registering the DLL using REGSVR32, which again gives the impression that the DLL has been registered. The ASP script continues to give the same message.
>
>We have tried unregistering, rebooting and registering the DLL again. No joy.
>
>The only difference we can see is that the client's server has two processors. Is there an issue with multiple processors and VFP applications/components ?
>
>Best.
>
>Matt.

Matt, in addition to unregistering, make sure that there are no registry entries (related to the DLL) left, before you try to register it again.

Also, single-treaded DLLs are almost useless, as you cannot even instantiate it second time within the same application without releasing the existing instance first. If you create it for Web application then (depending on purpose) you pobably should use MTDLL under MTS, as Claude says.