VBA is therefore different from the Standalone Visual Basic program used(by professional programmers) for developing commercial quality software applications _ though it borrows many of the latter's features. Think of Excel VBA as being the standalone Visual Basic software, built into Excel for the benefit of Excel users who are not necessarily programmers, but who are keen to exert more control over the application. So, Excel VB offers any interested users the necessary tools to make the application deliver more functionality. The final product is still an Excel document, but with extra functionalities added using VBA.
You will find this article of considerable reading value, if you belong to at least ONE of the following spreadsheet user categories: Owners of Small Businesses _ Restaurants/Bars, Hotels, Hospitals, Factories, Consultants etc; Decision Makers/Job Holders in Corporations _ Materials Managers, Sales/Marketing Analysts, Financial Analysts/Accountants, Project Engineers; And Anyone desiring to make BETTER sense _ and use _ of data!
Automating Your Spreadsheet Document : What is Excel VB? Microsoft Excel is a powerful tool for recording, organising/re_organising, analysing and presenting information. By Excel VB, I refer to Excel VBA _ where VBA means Visual Basic for Applications(VBA). VBA refers to the highly extensive and flexible macro programming language developed by Microsoft for use in their MS office applications _ Word, Power Point, etc.
Another question I ask, in answering the "Why Excel VB?" question is : "Why re_invent the wheel? ". My experiences(and those of others who favour the use of Excel VB like I do), confirm that to organise, and analyse data for (financial/management) report generation and decision making, you will save hundreds of hours using already in_built, pre_programmed Excel functions compared to a situation where you used Visual Basic proper. All the functions needed to achieve the above purposes already exist in Excel, so that you don't have to write them all from scratch as would be the case if you were to use Visual Basic. 3.It works even when you lack "In House" expertise.