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.
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.
The assignment was not an accident. Before being redeployed to Benin brewery, I had been involved in "validating" the numerous complex formulas in the custom Lotus 1θι spreadsheet application during its development. The author _ Richard Chambers _ was at the time in charge(as Training Coordinator) of training new entrants, and upon discovering my keen interest in learning, often gave me his laptop to "proof" formulas, links etc. It was he who had told his counterpart in Benin brewery(Joe Sheehy) that I could help out with a problem they were having using the application. And I did resolve the problem _ resulting in my subsequently becoming responsible for the reports collation using the application.
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.