Hi Scott,
Thankyou for all of your help with this.... it seems to be a question that
no one is realy interested in answering.....
I have managed to make my web service work by using a work-around and
returning an XML document instead of a data set.... this is not ideal by any
means, as the changed data has to be manipulated in code when it is returned,
instead of the automatic functionality of the dataset...
It seems that InfoPath does not like the WSDL information generated by the
Web Service for the dataset, especially the "s:schema" reference from inside
the s:schema type....
It also did not like the data with its diffgram tags when I saved a copy of
the WSDL and edited it. (This allowed data access, but InfoPath could not use
the data).
I am using .NET 2.0 and ASP.NET 2.0 with Web Designer Express 2005 to create
the web service.
From my reading, I thought that the problems with InfoPath and ADO.NET
datasets had been resolved with SP1, but it looks like there might be some
new problems with .NET 2.0 or ASP.NET 2.0
Suggestions welcome, as I would like to use datasets idealy.
Kevin