Should I use collections ?

[Tinbeard]

I'm about to start writing my first 'useful' application, the project is some service management software which will enable the user to maintain a customer database along with their associated contract details. The main funtion of the application is to manage the equipment faults for theses contracts, it will be able to raise new faults and allocate them to one of the engineering staff as well as maintain a complete fault history for each customer.

I'm going to use a SQL database, the question is should I create collections for the customer , contract, fault etc to hold the data or just use a data table for each. I know this question is a bit vauge but I'm thinking of just using datasets and data tables but this would put everythig into one big class, is this good practice ?

[The_Duck]

It is fine to put multiple tables inside a dataset. I tend to group logical items together. For example I would have a customers dataset, and a faults dataset. Thus you mught have a table

Customer
CustomerID
Customer

CustomerDocument
DocumentID
CustomerID
Document

etc

and a faults table

FaultType
FaultTypeID
FaultType

CustomerFaults
FaultID
FaultTypeID
CustomerID

hope this helps!

[Merrion]

If your not using objects and collections in your business layer you do lose a lot of the advantages of O-O programming (keeping your data and related methods for each "thing" in one place) and lose some flexibility.

There is a code example I have posted for serialising objects and collections to/from SQL tables that might help you..

[Tinbeard]

Thanks for your input on this, I'll check out your code sample.