G
Guest
Hello NG!
In a DataSet I have the tables A, B und C.
Table B is related to A with DeleteRule=Cascade
Table C is related to A with DeleteRule=None
This way an exception is thrown, if you try to remove a Row in A and there
are depending ChildRows in C. But ChildRows in B are already removed before
that exception is thrown.
So after that action I still have a Row in A, I still have ChildRows in C,
but I have no ChildRows in B.
Is there a possibility to check ALL relations, before the whole
removing-action is performed? Something like a transaction.
Please notice, that that problem is related to the .NET-CompactFramework,
which in my opinion does not know, what's a transactions, does it?
Any suggestions?
Thanks, D.Barisch
In a DataSet I have the tables A, B und C.
Table B is related to A with DeleteRule=Cascade
Table C is related to A with DeleteRule=None
This way an exception is thrown, if you try to remove a Row in A and there
are depending ChildRows in C. But ChildRows in B are already removed before
that exception is thrown.
So after that action I still have a Row in A, I still have ChildRows in C,
but I have no ChildRows in B.
Is there a possibility to check ALL relations, before the whole
removing-action is performed? Something like a transaction.
Please notice, that that problem is related to the .NET-CompactFramework,
which in my opinion does not know, what's a transactions, does it?
Any suggestions?
Thanks, D.Barisch