Yes, in my opinion. VBScript is just a scripting version of VB. There are some minor syntax differences, a few limitations (since it's not full blown VB), a few different built-in functions, and a few minor language differences (for example, all variables are variants - there are no specific types). Even with the slight differences they are very similar. If you know VB, it's easy (IMO) to work with VBScript.
Stated roughly: VB is a compiled language. You write code and compile it to an EXE to distribute it and use it (unless you just run it and use it in the IDE, in which case it's compiled as needed behind the scenes). A scripting language, like VBScript, is interpreted, which means it's compiled/interpreted on-the-fly by a scripting host (some program or Dll that's called when needed to do the interpreting).
"The main difference between VBS and VB is that VBS is for the web."
Not true. You can write .vbs (text file with .vbs extension) full of VBScript that can execute with a double-click (or as a scheduled job). For example, you might write a .vbs instead of a batch file to automate a simple task for windows (if you didn't feel like writing a program). Incidentally, with the right tools one can use VB to handle server-side processing for the web (VB CGI), it's just kind of a pain in the butt (IMO) and ASP is a lot easier to code and manage.
VB6 has a project type called "IIS Project" which involves a little known (and little used) technology called 'web classes' that do server-side processing for the web similar to ASPs in full blown VB. One problem with web classes is that they compile to a DLL (can be a pain to update compared to a text/ASP file) and they have some clunky syntax issues (IMO).
Lastly, one can write ActiveX Dlls in VB and create objects from them in ASP/VBScript...to use VB indirectly in a web setting.
"They are similar. No intelli-sense though."