Error 1: Falling into the interface design trap. Beautiful girls like to wear beautiful clothes, and ugly girls also like beautiful clothes. However, ACCESS does not provide any custom key functions except for custom menus and switch panels. If you want to use your own buttons, you have to write a lot of code, which is very troublesome. Why, why do you always put ready-made menus without using them, but have to write a whole interface yourself. Are you tired or not? Is it worth it, is anyone willing to pay more for your interface?
Error 2: Use ADO instead of DAO. Please remember that DAO is the most efficient database engine in the world to access mdb files, because DAO is directly embedded in the ACCESS running environment. Using ADO in ACCESS is like calling a colleague sitting opposite a table, and is deliberately walking a long way.
Error 3: Instead of using mdb database, use SQLSERVER. This phenomenon may only occur in China. Who says SQLSERVER2000 is only five yuan per card? In mdb's table, accessing million-level tables is absolutely fine. Is it necessary to use SQLSERVER for a department-level application system? Besides increasing the difficulty of development, I can't think of a better reason.
Error 4: Never use record change events. like:
BeforeUpdate user updates the record.
AfterUpdate records are updated.
A record updated by AfterInsert is a new record.
Proper use of these events can improve the robustness of the database. For example, in the personnel system, I want to save the salary change record. At this time, I just need to write code in the AfterUpdate event. There is no need to use SQLSERVER and then write the triggers inside.
Error 5: Use ACCESS to develop a system that will increase the amount of data quickly. The growth rate of the data volume of ACCESS system should be within 10,000 records per month. If the monthly growth of the application system you develop is greater than 100,000, it is recommended to use a large database system.
Error 6: Use ACCESS to develop non-simple database application systems such as entertainment programs and photo processing programs. VBA is just a subset of VB. Many VB functions are not provided in VBA. If VBA calls DLLs (ActiveX) in large quantities, it will reduce the stability of the system and it is easy to crash. Please always remember that ACCESS is only suitable for database development.