In addition to the Object Browser, you have the VBA help files (provided that it was installed as that is not the default option) These help files gives some general information about what the various objects/methods/properties/events/statements/keywords/miscellaneous are used for. One thing I have noticed to be missing from the help files starting with Office 2000, it doesn't seem to list the various arguments within the events and what they are used for. I had to look online (msdn.microsoft.com) for that info.
You also have within VB Editor, the Project Browser, which allows you to view the various "Class" objects (I.e. Forms, but not command buttons) in your project(s), and you also have the Properties window to view the various properties of an object that's selected in the Browser window, provided that the object has been openned. With these objects, you can double click on it to bring up the module window related to the "Class" object. Once this window is brought up, you can click on the left side of the module window at the top to select the object (which does include all sub objects on the main object such as command buttons that's on the form), then in the right top combobox, select the related event that you want to put code in for.
Of course, there's other ways to achieve the same event selections, but what I mentioned here is just one of the ways to do it.
Now onto Debugging tools:
You can use the immediate window for small minor tests such as what does a particular property of a particular object return currently
?MyForm1.Textbox1.Value
The immediate window has helped me out in seeing how certain properties and functions works.
Watch Window:
You can use this window to see what are the different values of the various properties/functions/variables. This window has been proven to be helpful in 2 ways:
First, it allows the developer to see the results of the item that's in question as the code is being stepped through, and second, when looking for a particular value as far as what property holds it, you can also use this window and don't even have to have code running (unless the property is only set during run-time)
If you are having an issue with your code, you can use break points by clicking on the left side of the module window. When the code is running and comes to this break point, it will NOT run that particular line as it just stops there and takes you to the VB Editor with that line of code showing. An error message will also pop up at this time to give you the option to continue(if allowed), end, debug, or help.
Hopefully, this will help you get started.
Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000
When the going gets tough, the tough gets going.