I agree with what Gary said ... when I read this, I *also* thought of this in terms of implementing business logic in a DataSet, which is totally do-able if one desires to do so. IMHO, this has nothing to do with change-tracking really, so I'm not sure what you were getting at.

~~Bonnie



>t is relatively trivial to create a partial class belonging to the dataset that contains any/all manner of logic and behaviour related to the data objects in the dataset. This also provides extended advantages that were not available prior to .NET 2. For example, if/when the dataset is regenerated, you don't lose your additional logic because it is retained in your own partial class file.
>
>Thanks for the response. The reason I asked Bonnie is because she suggested earlier that change tracking should not be handled in a partial class but at the parent tier. Hence my question. ;-) To be honest I can see justifications either way.