March 5, 2021
Hot Topics:

Book Review: Beginning Visual Basic 6 Objects

  • By James Limm
  • Send Email »
  • More Articles »

With Visual Basic 6, objects are here to stay. Love them or hate them, we can't get away from them. Without exception, everything we deal with in Visual Basic is an object. The forms we draw our user interfaces on, the controls that we put on to the form, and even most of the system objects that we use, from time to time, to complete the shine on our applications - they are all objects.

Visual Basic's support for object-oriented development has come a long way since previous versions. We now have the ability to expose more than one interface from within an object, thanks to the Implements keyword (more on that later), and we can create our own custom events at runtime. Visual Basic has a lot to offer real-world programming situations.

The problem with the whole thing, though, is that the object-oriented programming world is still populated by PhD-toting gangsters. These guys would have you believe that objects represent a different world, as opposed to just a neat way to design and develop applications. We covered a lot of the theory in my previous book (Beginning Visual Basic 6, also published by Wrox Press), but this time around we're going to see it used in anger, see some real-world development done with object-oriented programming.

Let me tell you: OOP isn't that hard. It doesn't need that much in the way of background training, or patterns of deep thought. It's all a matter of common sense. Let's take a look at a real problem.

Page 2 of 9

This article was originally published on November 20, 2002

Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Thanks for your registration, follow us on our social networks to keep up-to-date