Microsoft Access isn't the solution for all database needs, but it is a great choice for many small and even large businesses. Unfortunately, IT people often believe many of the myths about it which makes it hard for managers to implement Microsoft database training.
Myth #1: Access Isn't a REAL Database
In the early days of database applications, you had to be a programmer to use one. The average person couldn't hope to understand the complex database languages involved. Microsoft saw this and set out to develop a database for everyone else.Many of the original Access developers were non-programmers. The application, like all Office products, was meant to be usable without needing to learn cryptic programming commands. Although Microsoft database training is often necessary, it's still easier to learn Access than to learn other database applications.
So we have a database designed by non-programmers to be used by non-programmers. This has caused many IT people to immediately dismiss it as a toy, often without ever using it.
Its usability and accessibility is precisely why it is a good choice for many businesses. Organizations with simple database needs don't need the complexity of a product like Oracle, or the cost of the database administrator that they'd have to hire to use it.
Myth #2: Access Is Only Useful For Personal Databases
This application is ideal for small databases, particularly those accessed by only one user. It is commonly used by consumers for such mundane tasks as tracking a DVD collection and examples used in Microsoft database training often illustrate these kinds of uses.However Access is also useful for a variety of larger databases as well. Although it is not technically an enterprise solution, it can still be used on a large network by multiple users. Plus it is a lot less expensive than a true enterprise database.
Myth #3: Access Databases Get Corrupted
To be fair, this is only half a myth. Access databases are not as robust as those from other products and can become corrupted if they are used improperly. If users and administrators follow a few simple rules, database corruption becomes nearly impossible.Traditional Microsoft database training should be supplemented by a collection of best practices and regular backups to ensure database integrity. A list of these practices is beyond the scope of this article, but can be found by consulting an experienced Access user.
Many of these corruption risks are due to server and network configurations. In other words, they are the responsibility of the very IT people who complain about Access corruption.
PUBLICATION GUIDELINES