The claims I make above are NOT exaggerated. They are in fact based on my personal experiences doing the foregoing (a). As an manager in the challenging, fast_paced manufacturing work environment of a corporate multinational (b). As a solutions developer for individuals and businesses who use MS Excel for their work.
It's not enough to have a professional with the technical skills to solve your problem. s/he also needs to have the right attitude and background/experience _ else the relationship will not work. This is where an Excel VB resource is more likely to add value to you. Most Excel VB Developers have backgrounds in management, accounting, engineering and other fields, which further equips them to be useful to you in "thinking up" better ways to apply your spreadsheet automation to get the most value for your business. You therefore need to choose the right developer, with the appropriate background to match your needs.
The visiting head of the technical function only needed to look at the most recently plotted point on the chart (relative to preceding ones) for a Key Performance Indicator like. Cost per Hectolitres brewed(One Hectolitre = 100 Litres), to know if the brewery had stayed within the approved upper limit of spend(plotted as a straight line target across the same period) or not. Discussions would then take place based on identified "Exceptions"(which could be "good" e.g. savings made or "bad" e.g. monetary loss due to materials over_used), and "Actions To Be Taken" to correct or maintain observed performances agreed upon.
I believe the foregoing are compelling justifications for choosing Excel Visual Basic over Visual Basic.