Hi,

I have recently started coding and designing the ,.NET based system
using different technology involved in .NET and well from the subject
line of this post, it is obvious that I am coming from a VB background.

I have many years of expirance in designing distributed system based on

VB, C++ and SQL Server but when I have tried .NET it is a complete new
exerince for me and I am not hesitant in saying this is a damm cool
stuff from MS.

Now in this regards, I got a question but I am really not sure what is
the case in .NET.

In earlier days, when I used to design classes based on limited VB
object based model, we used to create 2 different callses for one
business component. One class which is used for all database read
operation and another for database write, update and delete opeation.
Now, why we were doing this so because of the locking in database via
VB programs. if all database select operation id seperated from
database write operation it palces less locks and almost comes out
immediatly by removing database locks (Offcorse when all the VB dlls
are regirsted in COM+). Now I wanted know is this still applicable in
.NET.

For example, if I want to write a Cusomter business component, do I
still have to seperate  out the select and updates in seperate classes.

In earlier days, I used to designed a dll with following classes.

CustomerRead (Main class to read, exposed to world)
CustomerWrite (Main class to write, exposed to world)
CustomerSingleSelect - a calss which gets data from customer based on
primary key and always return me a sigle row
CustomerMultiSelect - a class which gets the data from customer where
select operation is not based on its primay key.
CustomerModify - a class to modify customer.

Belive me this approch was much faster then everything in one class.
But this was the case in VB time. Does this still a case in .NET?

Thanks & Regards,

pb