Jojo,

I see that Alex has already given you a good answer.

~~Bonnie



>Hi Bonnie,
>
>Talking of Datasets, if let say I have a PolicyHolder table with 50,000 records, how can I pull all the records and disconnect from my Database from C#/VB.NeT?
>
>Can you explain as there might be difference between a Datasets created with Delphi/Interbase and C#/VB/MS SQL.
>
>I just need an answer, please.
>
>Thanks.
>
>>>>Oh wait, I'd have a separate DataSet project too
>>>
>>>Bonnie,
>>>What are the advantages of this?
>>
>>Simply to keep separate functionality separate. We've broken down our app into the following structure:
>>
>>Business (server-side)
>>BusinessClient (client-side ... some of this is used by the server-side classes as well)
>>DataAccess
>>DataSets
>>WebServices
>>WinUI
>>
>>Under each of the above, things are further broken down by functionality. IOW, say that I have a Personnel module and a
>>Customer module. I'll have separate projects (.DLLs) for:
>>
>>Business.Customer
>>Business.Personnel
>>BusinessClient.Customer
>>BusinessClient.Personnel
>>etc.
>>
>>IMHO, the DataSets should be the same way ... separate projects. So, I'll have a DataSets.Personnel project and in this project I'll have all the various datasets I need for the Personnel module.
>>
>>Do you have a reason for not doing it this way?
>>
>>~~Bonnie