G
Guest
I have a dataset with 2 tables (father and child table) and a
relation between them with cascade for update and delete.
I also have a client application and a remote application.
If in the client application I delete a existing father's row and afterwards
create the same father's row with the same field values and a new child row
and call a remote application' method by remoting passing this dataset
(making the serialization), you will see that there is no child row in
dataset at the remote application's method.
I think serialization lost the child row. This is a terrible problem.
The child row is indeed there. I'm seeing the row in a datagrid and I also
put a
break point and saw it in the dataset table but after the seralization the
child row vanished.
But note that the child row has vanished only if I create the father's row
with the same field's value from the deleted father's row.
I'm using framework 1.1.
Can someone help me?
relation between them with cascade for update and delete.
I also have a client application and a remote application.
If in the client application I delete a existing father's row and afterwards
create the same father's row with the same field values and a new child row
and call a remote application' method by remoting passing this dataset
(making the serialization), you will see that there is no child row in
dataset at the remote application's method.
I think serialization lost the child row. This is a terrible problem.
The child row is indeed there. I'm seeing the row in a datagrid and I also
put a
break point and saw it in the dataset table but after the seralization the
child row vanished.
But note that the child row has vanished only if I create the father's row
with the same field's value from the deleted father's row.
I'm using framework 1.1.
Can someone help me?