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.
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.
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.
This last point in my opinion is ONE major benefit you must seek to extract, if you choose to engage the services of a developer. S/he should be able to help you develop (in_house) expertise needed to maintain the application AFTER s/he is gone. If you fail to ensure this, all your cost_savings from using the application might end up being spent paying the developer to maintain the application over time in the future!