The essence of an Access database

Access enthusiasts are proud of VBA. I think this is not a good phenomenon. VBA is only a subset of VB, there are many limitations, such as not support inheritance, not support pointers, do not support child type, etc. Using VBA to manipulate data structures outside of the Office family is very difficult.

Access enthusiasts are proud of VBA. I think this is not a good phenomenon. VBA is only a subset of VB, there are many limitations, such as not support inheritance, not support pointers, do not support child type, etc. Using VBA to manipulate data structures outside of the Office family is very difficult.

VBA is just an attribute of access. In fact, no VBA Microsoft can sell access as usual. With VBA, you just make access more personalized. Do not add too much functionality to VBA, although it can be implemented, you will be very tired. If you're not just an access enthusiast, or a programming enthusiast, you should also learn another language (Pascal or C or assembler) in addition to VBA, and you'll find a very wide World open to you.

The essence of access is its ability to quickly frame database applications, and a skilled access user can complete a small, complete database application in a single day, from tables to forms to reports to menus. In fact, you can also find that the code inside the Northwind is very small.

The most common in our daily life is the Micro database, the number of records does not exceed millions. In this small system, security, concurrency, and so do not have too many requirements, the most need to focus on is time and cost. and access just happens to be able to frame this kind of system very quickly.