#Visual basic for applications access code
They code quickly, have a QA process, and stay in communication with IT who now hates them slightly less then they hate Microsoft. You know who would know, your centralized VBA development group. Sure IT is going to argue that can’t be the case, but they don’t know, they are too far removed from the user’s process. I am taking an educated guess, that in the best of companies, eighty percent of that data has at one time or another been in an Excel spreadsheet with zero control.
Users are going to keep using Excel for important tasks, let’s say you move the General Ledger uploads off to a centralized application, pulling data from your big data warehouse. You have no methods and no one central department that oversees its use, its automation, its power to correct, modify and/or destroy important company data. The common approach is to slowly work through each process, assess the risk and automate away pesky Excel and the power it gives users. I have been working for very large investment banks for almost twenty years (when I say large think of the richest and then the second richest) and the amount of input that Excel has on those numbers is astounding only outdone by the amount of hatred IT has for Excel. What most of companies have done is to allow users the Excel option, but keeping the lock on the data, by controlling updates to the original data source – problem solved – ah – not really. Organizations, that have large scary IT departments, spend millions of dollars a year trying to throw a deadbolt over their data, while the business users (to a person) want that data in Excel, essentially giving them the power to change a six to a nine, thereby making a so-so quarter, rock-solid! “I know, they’re awesome, now how do you get them in Excel?” “Have you seen the new reports in Hyperion?”
0 kommentar(er)
