VBA is therefore different from the Standalone Visual Basic program used(by professional programmers) for developing commercial quality software applications _ though it borrows many of the latter's features. Think of Excel VBA as being the standalone Visual Basic software, built into Excel for the benefit of Excel users who are not necessarily programmers, but who are keen to exert more control over the application. So, Excel VB offers any interested users the necessary tools to make the application deliver more functionality. The final product is still an Excel document, but with extra functionalities added using VBA.
I believe the foregoing are compelling justifications for choosing Excel Visual Basic over Visual Basic.
In addition, visualise it having dynamic query/report drop menu interfaces, and a variety of custom buttons: for navigation(within and between worksheets), printing, data export (as PDF documents or spreadsheet files), saving, auto_data filtering, auto_charts plotting, auto_backup of files, user login authentication (for documents with sensitive or confidential content) etc.
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).
types of spreadsheet
excel budget templates