Posted by: Anonymous Coward
on May 13, 2005 01:40 AM
I'll second this opinion. I worked for a large financial services firm that used a lot of macros-and other customizations for a non-microsoft spreadsheet application. When they wanted to migrate to another office suite, this complicated the process.
For the large business, user education and a responsive IT shop can help here. From a large enterprise perspective, spreadsheets and single-user databases (MS-Access) can be bad. They result in inconsistent snapshots of data being held in silos around the business. (Bob's customer file in sales doesn't match Gene's customer file in accounting, etc.) In addition, end users like Bob and Gene may be doing their own Access programming and macro- creation. Finally, these all important spreadsheets could be stored locally and unbacked up on the user's machine.
If a fancy spreadsheet is being used for regular, routine, processing tasks that are essential for a business, a business should probably consider replacing it with a database and program that does the processing and is stored and regularly backed up on a network.
Re:Macro Recorder?
Posted by: Anonymous Coward on May 13, 2005 01:40 AMFor the large business, user education and a responsive IT shop can help here. From a large enterprise perspective, spreadsheets and single-user databases (MS-Access) can be bad. They result in inconsistent snapshots of data being held in silos around the business. (Bob's customer file in sales doesn't match Gene's customer file in accounting, etc.) In addition, end users like Bob and Gene may be doing their own Access programming and macro- creation. Finally, these all important spreadsheets could be stored locally and unbacked up on the user's machine.
If a fancy spreadsheet is being used for regular, routine, processing tasks that are essential for a business, a business should probably consider replacing it with a database and program that does the processing and is stored and regularly backed up on a network.
#