>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 Visual FoxPro-runtime-modules is missing), he might slip into the next trap. As he is going ARGHHHHalready, I thought this might be intersting.

Yes agreed. My bet is for a bad registry file

>>>
>>>3. You COM.Server will always start at C:\Windows NT\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 Visual FoxPro or another application on Your station"

Hum .. sorry but also nope, you can ... I'll try to explain myself.

Imagine in your server you have this scenario:

Local disc C:
Folder MYMAP shared as F: drive
folder MYMAP\MYWS and ws.dll

It can appear as:

C:\MYMAP\MYWS\ws.dll
or
K:\MYWS\ws.dll

Going to a DOS BOX ...

1. CD C:\MYMAP\MYWS
2. C:\MYMAP\MYWS>REGSVR32 ws.dll

If you look at Application.ServerName property he will start at C:\MYMAP\MYWS, and starting (like SYS(5) drive is C:\

second test

1. F:
2. CD MYWS
3. F:\MYWS>REGSVR32 ws.dll

If you look at Application.ServerName property he will start at K:\MYWS, and starting (like SYS(5) drive is F:\

So, the starting path and drive will depend from where you register the DLL in your server.

Regards,