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.
To experience the type of automation I refer to, you can email FREE demos of sample automated Excel VB driven spreadsheet applications like Ƒ) a Training Tracking Database(TM), ƒ) a Fiveƕ) Year Income & Expense Monitor(TM) or Ɠ) an Export Packing List & Invoice Generator(TM) to yourself using the file mailer on my website.
At times, they would prefer to click a button that says "Print ABC", or "Print XYZ" report, instead of having to crawl all over the huge spreadsheet(and get "lost" every now and then), to highlight and print different report pages. Using a custom built data entry form to make data entries into 14 different cells in different parts of a table(at the same time/with one click) would, for them, be "heaven" compared to making the entries one at a time.
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.