Hi Miha,
The 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.
Thanks.
Mauricio
ControlBase - Brazil
"Miha Markic [MVP C#]" wrote:
> Hi Mauricio,
>
> Before serializing check that row is indeed there.
>
> --
> Miha Markic [MVP C#] - RightHand .NET consulting & development
> SLODUG - Slovene Developer Users Group
> www.rthand.com
>
> "Mauricio Pires" <(E-Mail Removed)> wrote in message
> news:65193998-69B0-4254-B720-(E-Mail Removed)...
> >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.
> >
> > Can someone help me?
> >
> >
>
>
>