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.
So, (when considering the automation I speak about) do not think about spreadsheet documents containing one or two click_able buttons that allow a user print a page or copy some cells from one sheet to another. Instead, I want you to picture an application(or Entreprise Information System) that customises the appearance of your spreadsheet workspace(to take advantage of maximum screen capital available on your PC), and offers you custom "floating" data entry forms.
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.
This last point in my opinion is ONE major benefit you must seek to extract, if you choose to engage the services of a developer. S/he should be able to help you develop (in_house) expertise needed to maintain the application AFTER s/he is gone. If you fail to ensure this, all your cost_savings from using the application might end up being spent paying the developer to maintain the application over time in the future!
examples of spreadsheet packages
excel spreadsheet examples