Visual Basic

Microsoft Visual Basic, often abbreviated "VB", is a computer language and IDE. The latest version is VB6, which seems to be no longer (or minimally) supported; VB6's successor, VB.NET, is apparently a rather different language and not entirely backward-compatible.

Features

• Language
  • Event-driven
  • Supports object-oriented programming (although it is essentially method-based, and also does not support inheritance)
  • Unlike older BASIC varieties, does not require line numbers; can use text as labels just as easily
  • Supports required definitions, i.e. the compiler will give an error if you use an undefined variable
  • Supports variant-type variables which can store any data type
• IDE
  • Function fill-in popups which show:
    • all arguments needed by a function, subroutine, or method
    • which argument you are currently filling in, based on cursor position
    • Listing of available fields/methods: on typing the name of an object plus ".", a list of defined fields and methods will pop up

Pros

Good for writing business applications where correct implementation of somewhat complicated logic is more important than speed or elegance of design.

Cons

Many programmers consider using VB for development to be sort of like eating candy for dinner, for reasons that I can't think of at the moment. It does tend to allow a lot of a programmer's mental muscles to atrophy through inactivity, however.

VB is only available for Windows, so cannot be used for cross-platform development.

VB only produces GUI-based applications, and cannot be used to write text console (i.e. DOS mode) applications.

Problems

listed more or less as they come up

Place a treeview control on page 1 of an SSTab. Set page 2 as the default. If you want to resize the SSTab to fill the form and resize the treeview to fill the tab, you run into problems because the treeview's location (mainly the "Left" field) isn't set properly until page 1 is displayed, and there doesn't seem to be any systematic way of determining when its location data is correct. The treeview's "visible" property is set True even though it isn't actually visible. (Perhaps the SSTab is setting the Left field to a weird value in order to hide the treeview?)

Reference

• Wikipedia