You didn’t run out to the computer store and buy a copy of VBScript. You didn’t
install a VBScript disk on your computer, either. All you did was install the Internet
Explorer browser, which supports VBScript, on your computer–just like millions of
other folks. Everyone of them has the VBScript engine on their computer, and everyone
of them has the ability to create Web pages with VBScript.
So where’s the integrated development environment that you’re used to using in
Visual Basic? Keep looking, because there isn’t one. All you have is your favorite
text editor, the ActiveX Control Pad, and a Web browser. That in itself is the single
largest difference between Visual Basic and VBScript. It leads to some specific differences,
too. Here’s what they are:
- Debugging VBScript doesn’t have a debugger like Visual Basic. You’ll
resort to using lots of message boxes, instead. - Event-handlers You don’t have an editor in which you select an object
and event to edit an event-procedure. You have to name event-procedures in your scripts
so that the scripting engine can find the appropriate handler when an object fires
an event. - Forms VBScript doesn’t have a forms editor. It doesn’t need one, because
you can’t display forms anyway. You put forms and controls on the Web page, instead.
You can use the ActiveX Control pad to insert all those nasty