>My dll works fine as tested from VFP NewObject().
>I was getting the "Unknown COM Status Code" error - looked up fixes for that and seem to be past that.
>Now - I instantiate the soap object, soap-init my wsdl file, and try to run my method. I get an

OLE IDispatch exception code 0 from
>SOAP-ENV Server: Error source: Server..." 

error message back. that's all it says. I check the objects "Detail" property and get the following:
>
>failed HRESULT=0x800401F3 - WSDLService:The PROGID gcomws.gcomws is invalid
>
>I try to regsvr32 the dll ON THE SERVER (not sure why - seemed like a good idea) and that fails.

When I create a new webservice dll I do need to register manually that dll in the server at least once via the regsvr32. Assuming I created the webservice in a Workstation.

Maybe you can have more problems, but the first thing you need solved is having your dll properly registered.

So, check the next (in your server).

Look at your gcomws.VBR for knowing what entries are created in your server registry. Even the VBR is not needed for registering the DLL.

1. Search in your registry for occurrences of gcomws

2. Do you get some? or one? Unregister your dll

3. IISRESET (for stopping the IIS)

4. Delete gcomws.VBR, gcomws.tbl, gcomws.wsld, gcomws.wsml, gcomws.dll

5. Generate again the DLL (in your workstation)

6. register manually (regsvr32) gcomws.dll

If you can't get your dll properly registered now .. probably you have more bugs in your server registry. Consider to get a backup copy of that.

When you get your dll registered, then is time to think in IIS permissions, and so.

Hope this helps.