In addition, an Excel VB developer( who in many cases will tend to be a user turned developer, and is therefore likely to easily see things from your perspective) _ unlike a programmer _ is more likely to be positively disposed to working with you to ensure the application meets your practical needs. S/he will readily understand that the final application is meant to help solve a real problem(s), and will therefore build it to match those expectations.
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.
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.
Deciding What Spreadsheet Application To Use. This would ultimately be up to you. The big "fight" has always been between Lotus 1θι and Microsoft Excel. I started out with Lotus 1θι back in 1993 and learnt Lotus Macros programming(via self_tutoring). I eventually used this skill to develop _ in my free time _ various custom spreadsheet solutions(that were formally adopted for use in the departments I worked in as a brewer/manager in Guinness), before switching to Microsoft Excel in 2001. Subsequently, I developed my Excel Visual Basic spreadsheet programming skills (also via self_tutoring), because the company had chosen to adopt MS Office during the roll over to year 2000.
spreadsheet templates for tracking
uses of spreadsheet