Thanks Guys.

  • Thread starter Thread starter Jeff Brown
  • Start date Start date
J

Jeff Brown

CJ and others have pointed me in the right direction. After reading most of th book i bought last night i realized i was creating my own headaches by not seperating my data access, business logic, and presentation layers. I have finally came to an understanding with the new OOP practices available to VB .NET and now i am staring over and wring completely re-useable code throughout my project. And i just wanted to say thanks for you help and insight.

Jeff Brown

P.S. The book is pretty informative OOP: Building re-useable components with Visual Basic .NET, I haven't started reading the ADO.NET book as i realizeed my problem was not with ADO.NET but rather my architectual structure of my program.
 
Hi Jeff. The code is certainly more reusable/extendable/maintainable...but design time increases... :)

Derek LaZard
CJ and others have pointed me in the right direction. After reading most of th book i bought last night i realized i was creating my own headaches by not seperating my data access, business logic, and presentation layers. I have finally came to an understanding with the new OOP practices available to VB .NET and now i am staring over and wring completely re-useable code throughout my project. And i just wanted to say thanks for you help and insight.

Jeff Brown

P.S. The book is pretty informative OOP: Building re-useable components with Visual Basic .NET, I haven't started reading the ADO.NET book as i realizeed my problem was not with ADO.NET but rather my architectual structure of my program.
 
Figured that much out, but i was designing different clients anyway (web client - Intranet, Win32, data for a Internet Site also to be done, i already had it planned just wasn't sure how to implement. By doing this way me design time hasn't really increased but my coding time has shortened tremendously as i can now just resuse certain code for each interface.
Hi Jeff. The code is certainly more reusable/extendable/maintainable...but design time increases... :)

Derek LaZard
CJ and others have pointed me in the right direction. After reading most of th book i bought last night i realized i was creating my own headaches by not seperating my data access, business logic, and presentation layers. I have finally came to an understanding with the new OOP practices available to VB .NET and now i am staring over and wring completely re-useable code throughout my project. And i just wanted to say thanks for you help and insight.

Jeff Brown

P.S. The book is pretty informative OOP: Building re-useable components with Visual Basic .NET, I haven't started reading the ADO.NET book as i realizeed my problem was not with ADO.NET but rather my architectual structure of my program.
 
Back
Top