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.
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.
From this point on, I will refer to only one of the above mentioned applications, because it is my preferred work environment. That is Microsoft Excel. I believe users of other spreadsheet applications will be able to adapt whatever I say from here for use in their own peculiar environments.