Dataset Errors and webservices

  • Thread starter Thread starter Ian Cox
  • Start date Start date
I

Ian Cox

Hi,

I have a component that takes a dataset and updates it. It
handles the concurrency update issue by setting the
RowError property during the RowUpdated event.

This all works well when it is called directly from a
windows client. If I create a webservice to wrapper the
component then the webservice fails when the RowError
property is set.

Any ideas please
Ian Cox
 
Hello Ian,
This has been brought up by others and myself and I have yet to see any
response from Microsoft. You are probably getting "xml not well formed" or
something to that effect. Kathleen Dollard (mvp) responded in the
dotnet.general group to the message titled "repost: Problem Retrieving
DataSet Returned By A WebService" indicating that she could see the problem
but I never saw any other responses as far as a solution or even
acknowlegement from MS that they were aware of it and looking into it.

I am almost certain that it is a serialization issue but I do not have an
answer for you. I really hope that this can be resolved as the row/column
errors are a powerful tool that, in the case of webservices, is broken.
Since all of my users were going to be "windows" based, strongly typed
datasets seemed to be ideal containers for data but as you have found,
dataset errors presents a problem through webservices so I had to go back
and rethink my return values from webservices.

Reproducing the problem is easy enough. Create a webservice call that
returns a dataset and test it. Now, add a row error to the dataset before it
is returned from the service and you will see the error.

Roger
 
Roger,

Ms Strike again. Provide an excellent facility then make
it un-useable. Should you hear of a solution please let me
know.

Many thanks
Ian Cox
 
Back
Top