Access developers often make mistakes encyclopedia _asp basics

Error one: Caught in the interface design trap. Beautiful girls like to wear beautiful clothes, ugly girls also like beautiful clothes, access in addition to providing custom menu and switch surface version, does not provide any custom control key function. If you want to use your own buttons, you have to write a lot of code, very troublesome. Why, why, do you always have a ready-made menu instead of writing a whole interface yourself? Tired not tired. Is it worth it, is there anyone willing to pay more for your interface?

Error Two: Do not use the DAO, but use ADO. Keep in mind that DAO is the most efficient database engine for accessing MDB files in the world, because DAO is embedded directly in the Access Runtime environment. Using ADO in Access is like calling a co-worker sitting across the table, deliberately taking a walk.

Error Three: Do not use the MDB database, and to use SQL Server, this phenomenon may only be in China, who is called SQL Server 2000 only five Yuan. In the MDB table, access to the millions level table is completely fine. A department-level application system, is it necessary to use SQL Server? In addition to increasing the difficulty of development, I can't think of any better reason.

Error Four: Record change events are never used. Such as:

BeforeUpdate the user to update the record.
After the AfterUpdate record is updated.
The AfterInsert update record is a new record.

Reasonable use of these events can improve the robustness of the database. For example, in the personnel system, I want to keep a record of changes in wages, then as long as the AfterUpdate event to write code on it, there is no need to use SQL SERVER, and then write the trigger inside.

Error Five: The system that uses access to develop data volumes will quickly gather growth. The amount of data in an access system is best recorded within 10,000 records per month. If you develop an application system with a monthly growth record of more than 100,000, it is recommended that you use a large database system.

Error VI: Use Access to develop a non simple database application system, such as entertainment programs, photo handlers, and so on. VBA This is only a subset of VB, a lot of VB features VBA does not provide, if a large number of VBA call DLL (ActiveX) will reduce the stability of the system, it is easy to panic. Always keep in mind that access is only suitable for database development.