Matt,

MTS is not a necessity. You should have yourApp.dll,yourApp.vbr,yourApp.tlb,VFP6T.dll,and VFP6RENU.dll in that directory. Regsvr32 VFP6T.dll and then yourApp.dll. That should do it!
>Hi Nick/Claude
>
>>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.
>
>We have the runtime libraries in the same directory as our DLL.
>
>I'm not sure how we would find registry entries relating to the DLL - do we just search on the name of the DLL and the name of the class ?
>
>I'll take your advice re. using MTDLL, but how do we use it under MTS ? Is MTS a standard component of a Windows NT installation ? Also, the single threaded DLL appears to work ok on our test NT and 2000 servers - we have even tested on a freshly installed server with no problems.
>
>Best.
>
>Matt.