>
>These steps are a second phase, If Ken has problems registering the DLL this is the first he must solve.
>

Yes true. If the COM Server is not running at all on the other station there's no need
to look for the rest. But as soon as that is solved (witch mostly is because one of the
VFP-runtime-modules is missing), he might slip into the next trap. As he is going ARGHHHH
already, I thought this might be intersting.

>>
>>3. You COM.Server will always start at C:\WINNT\SYSTEM32 no matter where it actually is.
>>
>I'm not agree here ... if you generate a single threaded WebService DLL, he wil star
>wenever from you register it in your server.
>

I never tried that. Maybe I should have said: "You can't be sure that the default-directory
is where it is when You call Your COMServer locally from within VFP or another application
on Your station"