Thanks for the response. I'll try some of these things and see if I can get it to work.


>Steve
>
>>I can't seem to get my COM object to work as a Web Service. I have tried generating both from the VFP Wizard and directly from the ToolKit Wizard. The WSDL and WSML files look fine - all of my methods are correctly defined there - but when I create a reference in VFP, IntelliSense doesn't show them and I get "Unknown COM status code" errors when I try to call them.
>
>Check these:
>
>- did you create a multithreaded DLL and probably forgot to
> install VFP7T.DLL on the host system? or a single-threaded
> and forgot vfp7r.dll respectively.
>
>- Try regsvr32 on the host and see if You get "... succeeded"
>
>- open the WSDL on the host with a normal editor and go to the very end.
> have a look at the
> >
>- Try something very easy first. Functions like these
> PROCEDURE WhatTime as String
> return sys(0) +" # "+ ttoc(dateTime())
> ENDPROC
>
> or
> PROCEDURE WhereAMI as String
> return sys(5) + curDir()
> ENDPROC
>
>- I found that the wizzards sometimes do not hook the WSDL-Extension
> to the IIS properly. Open IIS, select Your virtual folder, rightclick
> on it and choose properties.
> On the "virtual directory"-tab find and click the "Configure"-button.
> You should see a list of all the registrered extendions. See if You can
> find .WSDL in that list.
> If not, click "add" and enter the path (!!DOS-PATH!!) to the file
> SOAPISAP.DLL in the MSSOAP\BINARIES subdir.
> In Germany the standard is
> C:\PROGRAMME\GEMEINSAME DATEIEN\MSSOAP\BINARIES\SOAPISAP.DLL
> and I have to enter
> C:\PROGRA~1\GEMEIN~1\MSSOAP\BINARIES\SOAPISAP.DLL
> in order to make this work.
>
> On my IIS I have:
> Programm: C:\....\SOAPISAP.DLL
> Extension: .WSDL
> ScriptModule: checked
> check this file first: unchecked
>
>
>
>HTH