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.
1. The Pareto Principle _ Using spreadsheet tracking, you can easily apply the Pareto principle in deciding which of your income sources and expense channels(i.e. products and services sales) to focus on in order to maximize profits. Considering that you are most likely to use the same marketing/sales resources to serve your customers, it only follows that if you focus on your biggest margin selling products/services, you will get increased profits at more or less the same cost.
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!
Why Excel Visual Basic _ and NOT Visual Basic? I always answer this question by asking the following question: What would be the point of "Killing A Fly With A Hammer"? Let me elaborate. If a method is available that allows us to achieve the same desired result(s) at LOWER cost, with LESS effort and in LESS time, why should we fail to adopt it? Certain IT persons insist that developing executable applications using the standalone Visual Basic programming language is "better" as it does not limit the user to a particular user application software environment. I concede that this might be a valid point under certain conditions. However, I point out that there are many users who have peculiar needs that do not necessarily require complex solutions. A lot of people today simply want to get their data recording, (re)organisation, and analysis for decision making done quicker and with less effort. They also want to spend as little money as possible to do this. In other words, they want a cost_effective solution that gives them independence from the solution provider in the long term _ without requiring them to undertake laborious skills acquisition immediately. This category of everyday users of technology described above are the ones I believe need Excel VB solutions of the type I describe. One expects that some of these users will over time develop an interest in acquiring advanced skills needed to develop their own solutions in future _ which is why I also encourage them to do so, possibly via self_tutoring, like I did.