I believe using either of these two applications should not pose any problems for implementing your spreadsheet automation ideas. This is because both have always been "friendly", towards making it easy for users to get more functionality out of them by way of custom programming.
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.
Custom spreadsheet solutions which survive long after the developer has "left the scene", are often those which users accept because they discover it _ among other benefits _ makes their work quicker and easier to do. That is why the best person to develop such solutions tend to be one who works in that area, and is therefore familiar with the way the manual system operates. S/he would have an "insider's" perspective of the best way to introduce automation other users will readily adopt _ even as it solves the identified problem(s).
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.
types of spreadsheet
uses of spreadsheet
what is spreadsheet in excel