M
Mat
I'm having difficult with these cascading keys, but it maybe I'm too
hopeful as to their capabilities.
Situation;
A typed dataset, containing two complex types which.
TableA, columns (AppID int , Reference string)
TableB, columns (AppID int , Description string)
If within the code I create the dataset, and populate TableA with the
Reference. I then create TableB, populate the Description and set its
parent to be the first row within TableA.
It is then possible to give the row within TableA and have this
cascade down to the child row in TableB. I've tried this setting the
AppId in row0 of tableA and checking the dataset XML (also tried
applying the changes via AcceptChanges) and it doesn't seem to be
happening for me...but maybe I'm missing something.
Any ideas?
Cheers,
hopeful as to their capabilities.
Situation;
A typed dataset, containing two complex types which.
TableA, columns (AppID int , Reference string)
TableB, columns (AppID int , Description string)
If within the code I create the dataset, and populate TableA with the
Reference. I then create TableB, populate the Description and set its
parent to be the first row within TableA.
It is then possible to give the row within TableA and have this
cascade down to the child row in TableB. I've tried this setting the
AppId in row0 of tableA and checking the dataset XML (also tried
applying the changes via AcceptChanges) and it doesn't seem to be
happening for me...but maybe I'm missing something.
Any ideas?
Cheers,