I have used KB article: 320301
(http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;320301&product=vcSnet)
as as reference to update datsets with nested relationships. So far
it works great for the case of a simple parent-child relationship
between two tables in a dataset. I have a couple of questions:
-Is this a temporary work-around until a permanent solution is
provided?
-Is there any negative impact on using this code example to handle
relationships of higher depth than parent-child relationship? For
example, lets say you have a table named "UnemploymentClaim" that has
a child named "worker" that has a child table named "address" that has
a child table named "zipCodes". (I know I am reaching here, but
hopefully you get the point). The question here is will the same
methodology that is used in KB article 320301 work for the
relationships that I described?
I would really appreciate any input on this matter because I am
looking into using this on a larger scale...
Thanks,
Bill