I believe the foregoing are compelling justifications for choosing Excel Visual Basic over Visual Basic.
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.
A DIFFERENT Type Of Automation. The approach to spreadsheet automation that I refer to, is one that seeks to provide functional spreadsheet automation alternatives for ANY spreadsheet user task(s). Typically, solutions like this would require the developer to study existing manual data recording, analysis and report generation systems, then plan _ in consultation with users _ for incorporation of automation into the spreadsheet to replace them, where possible.
The savings _ from using your "in house" expertise _ in terms of money and man_hours alone, will quickly justify the investment you make in "developing the needed skills" _ especially, when you compare what you spend with the cost of purchasing a commercial software application _ or even engaging the services of an Excel VB developer.
spreadsheet templates for tracking
blank spreadsheet templates