N
Nathan Phelps
I have a typed DataSet that contains approximately eight DataTables with
foreign key relationships that I am returning from a ASMX web service to a
Winforms application. The rows of a few particular tables don't seem to be
making it across the wire.
* I can verify that these particular DataTables are being populated
correctly by their DataAdapters by debugging on the server-side and
verifying that the XML returned from the web service call includes the rows
in question (tested using the test page generated by ASP for the web
service).
* I can verify that the typed DataSet that is generated by adding the
reference to the client project includes the appropriate definition of the
tables in question.
The rows in these tables, however, don't make it across the wire. I can
verify this by calling WriteXml on the returned DataSet and examining the
saved file to find that the rows in question are missing.
I have tried removing the web reference and recreating it, removing all the
foreign key relationships in the DataSet, but I get the same results...
Any ideas?
Thanks,
Nathan
foreign key relationships that I am returning from a ASMX web service to a
Winforms application. The rows of a few particular tables don't seem to be
making it across the wire.
* I can verify that these particular DataTables are being populated
correctly by their DataAdapters by debugging on the server-side and
verifying that the XML returned from the web service call includes the rows
in question (tested using the test page generated by ASP for the web
service).
* I can verify that the typed DataSet that is generated by adding the
reference to the client project includes the appropriate definition of the
tables in question.
The rows in these tables, however, don't make it across the wire. I can
verify this by calling WriteXml on the returned DataSet and examining the
saved file to find that the rows in question are missing.
I have tried removing the web reference and recreating it, removing all the
foreign key relationships in the DataSet, but I get the same results...
Any ideas?
Thanks,
Nathan