Visual Basic:
The Visual Basic programming language have been chosen by the MultiValue Environment due to its ease of use and the MultiValue BASIC-like programming structure. With little extra work, a MultiValue programmer can write Windows programs using Visual Basic without having to relearn how to program in a different language syntax, for example Visual C++.
Visual Basic programs are free standing programming environment. Windows programs can be compiled and the programs can be exported to other Windows platform. VB programs run in their own memory space, and can be written to run on both 16-bit (Windows 3.1) and 32-bit (Windows 95/98/NT) platforms. They can even run on RISC platforms running on Windows NT without changing any of the existing programs.
Visual Basic also allows programmers to make Custom Controls to be used in other Visual Basic program, as well as Delphi and Visual C++. Using Visual Basic Enterprise, programmers can create n-tiered systems. This allows programmers to create programs that communicate with each other across a network to share information and resources as well as work in unison. This is useful in splitting the client and server processing thus speeding data access for users.
Visual Basic has taken out most of the multi-tasking and multi-threading complications that C++ programs normally have to contend with. It also deals with the memory issue that the higher level languages have.
VBA:
Visual Basic for Applications (VBA) is more than just the Macro Language it is most commonly thought of and used as. It has the same abilities normal Visual Basic except Visual Basic for Applications programs can not be compiled into Executables or DLLs. Visual Basic for Applications also doesn't run in its own memory space as a normal Visual Basic executables would.
VBA is a part of the application it is shipped with; for example, Office or AutoCAD. VBA programs run as a DLL (or in the same memory space) to these applications. Thus the overhead in accessing these host programs is less cumbersome and quicker than a pure Visual Basic using OLE.
Why would a programmer choose Visual Basic for Applications as opposed to Visual Basic? VBA is finding its way into more and more applications. Since VBA is actually a part of the application (ie. Microsoft Office, AutoCAD, etc.), the overhead is lower which makes accessing and manipulating the host application faster. It also gives users greater ability to manipulate the host application. For example, adding new options to the menu bar or the tool bar.
Normally VBA programs are saved in the same file as the data. An example of this is Excel spreadsheets. When that data file is transferred to someone else, the program goes with it. Since not all workstations may have the same Windows programs loaded on them, this is a big advantage when users move the data from computer to computer or client to client. This way, the VBA program gets transferred with the data.
A Visual Basic programmer can write VBA programs. However, without intimate knowledge of the Objects supplied with VBA the programmer will be unable to make optimal use of the VBA programming environment.
Hope this info helps you ! ! ! ! !
Regards,
Basha
