Business Scenario 1 - When Excel hits the wall
Companies of all sizes are now putting a PC with office suite software on every desk. As the need for all sorts of data increases, over-burdened Information Systems (IS) groups are pushing responsibilities for data processing out to non-IS personnel.
PC users generally know Microsoft Excel, so that’s what they use to manage data. Often the data being managed involves relationships, but is kept in a “flat” format. Many spreadsheets are linked together requiring significant maintenance of the system as data requirements change and expand. These “databases” become unwieldy due to size and complexity.
Databases of this nature can be smoothly converted to Access database applications. The data can be imported from Excel into Access avoiding time consuming and costly re-keying. It will then be in a well organized relational format.
Business Scenario 2 - My current system works well, but…
Companies purchase off-the-shelf software packages for various applications. These packages generally provide many functions and features at a relatively low cost. Often, however, one or more requirements are not met by this type of software and it cannot be modified.
Access provides a flexible solution. A custom designed database application can be developed which will exchange data with the main software package. Data can be imported from the main database for custom reporting requirements, or transactions can be entered in an Access database and exported to the main database.
Business Scenario 3 - I already use Access, but it’s not my job
Some individuals recognize that Access is the appropriate tool in the office suite for developing database applications. Databases are developed in “spare time” while performing other duties. Much time is invested and the resulting database is functional, but not user friendly, making it available to only the most computer savvy.
These “home grown” databases are difficult to extend and maintain. Their ongoing usefulness and availability is dependent on the original developers who may or may not have time to support and enhance them.
Such databases can be reorganized and given a “face lift” while maintaining the original investment. The data is normalized and a user friendly front-end interface is added.
|
