Hi, David.

>The whole point is to have a place to put behavior (business logic and rules like the RaiseCreditLimit) together with the data that it acts upon (in this case the data inside the dataset).
>
>Just remember that the DataSet is a relational thing (made up of tables, rows, and columns) and it is not an object-oriented thing so if you base your application on DataSets it will still be a relational application, not an object-oriented one.

I absolutely agree. Indeed, it smells terrble bad when you see a method like GetDataset() in a business object. OOP is all about encapsulation and abstraction in general, so having a method whose name refers THAT badly to the implementation should be like a fire alarm for anyone.

Talking about what... aren't you willing to write about domain model fo UT Mag? 8-)

We're still missing you, David. Drop me a line whenever you have a couple minutes.

Best regards,