Case Study : To Access or not to Access
Love it or hate it, there are some places where Access just shines out as a handy tool. For example, if you have a corporate system which contains masses of useful information, but you can’t find a way to ask it for the details you need. If you are allowed to link into its database for read-only use, then Access would be a good tool to allow you to query and report from the database.
If you need to pull data from a spreadsheet into a corporate system, but it’s not quite in the right format, Access can talk to both of them and move the data for you.
It is great at connecting to other databases, and also to files like spreadsheets. If you are looking for permanent links to a database, then consider security issues, since some links like ODBC might not provide the level of security you require. However if you are using Access as a temporary link while transferring data this should not be such a concern.
One of the reasons companies adopt a “no Access databases” policy is their concern about important information being held in local databases by different people in the organisation, when the company would benefit from having this data in a central place. The reason people do this is usually to do with some real or perceived inflexibility in the central system.
If Access was linking in to the central system, rather than separately duplicating information that should be held there, then perhaps it would provide the querying required, and provide it very cheaply too. |