Don,

I've not used VFP Web Services from .NET, but I'm wondering why you added a regular reference instead of a Web Reference. If you want to use the VFP Web Service (and I assume that you do), then shouldn't you be adding a Web Reference?

~~Bonnie


>HELP
>
>I've worked w/some samples and things are starting to click, but now I've got a problem.
>
>I started a brand new VPF project. a single OLEPUBLIC class and a single function (aside from init to set the startup path directory). In that method, I have it accepting 2 parameters and have a simple RETURN 1 -- just for grins and no complex error from bad select, file not found, etc type of errors...
>
>I build the project into an EXE. Then, with the SOAP 3 Toolkit, I ran the WSDL generator against the project. Set appropriate 127.0.0.1/virtualdir pathing info and WSDL info build ok.
>
>In the .Net app, I added a "Reference" (as opposed to a WEB Reference) and chose the COM object. In the click of the code on the .Net web form, I created the COM object, called the method and set a caption on the form to the return value -- all ok to this point.
>
>Now, I go back to VFP, update the code to actually perform some SQL validation, querying, etc but still return a number as before. Recompile the project in VPF. Go back into .Net and run the web forms and I get the proper result from the newly compiled code.
>
>NOW THE PROBLEM.
>
>In VFP, I add a NEW method to the class, put simple code in that too and regenerate the EXE. I re-run the SOAP 3 toolkit for WSDL and get those files updated. In .Net, it now recognizes the new method.
>
>In the code on .Net, I make a call to this new function, rebuild and run. Now, I get an error in .Net
>
>"The supplied user buffer is not valid for the requested operation."
>
>
>HELP!!!
>
>This is really p'ing me off...