Visual Basic Programming: Much Ado about ADO
(Page 1 of 5 )
Author Maneesh Makheeja delves into ADO concepts from a Visual Basic programming perspective to how the injudicious use of ADO objects and methods affects not only the execution but also the performance of a Visual Basic program. The author looks at some common slip-ups that often cause problems in the Visual Basic code.
The ADO architecture makes the very heart of application development in Visual Basic that involves interaction with the databases. Considering that ADO acts as an interface between a Visual Basic application and the data source, providing all the objects and methods of data access, the whole business of database manipulation in Visual Basic environment thus comes to hinge on the ADO architecture.
The know-how of ADO concepts often draws the wedge between an erroneous piece of code and a perfectly working Visual Basic program. This is for the simple reason that creating and using ADO objects and methods indiscriminately and without much idea about their scope and usage makes Visual Basic programming a thorny affair. One wrong move, and an error pops up, which might seem senseless.….unless you understand the ADO architecture to the core. So the answer to that ubiquitous “what the heck is wrong with my code” often lies in how one creates and uses the ADO objects and the associated methods.
This article delves into ADO concepts from Visual Basic programming perspective. It is assumed that the readers already have an elementary knowledge of the ADO architecture and Visual Basic environment. We shall see how the injudicious use of ADO objects and methods affects not only the execution but also the performance of a Visual Basic program. Let us have a look at some common slip-ups that often cause problems in the Visual Basic code.
Next: Not Specifying the Library Being Referred To >>
More Visual Basic.NET Articles
More By Maneesh Makheeja
/ 40 
