A family of Microsoft relational database management systems designed for ease of use.
It's ironic, but mastery of Excel can initially be an impediment to success with Acccess for two reasons.
- Excel is a flat file, which means it stores data very differently from the optimal method of storing data in a relational database such as Access. If you start out with flat file, "Excel-like" tables in Access, the result will be less than good.
- VBA in Access and Excel are similar, but the majority of formulas in Excel have no real counterparts in Access, and vice versa. If you start out expecting to simply leverage familiarity with Excel formulas in Access, you run into dead-ends.
I've used the term "application bias" to refer to this phenomenon. By that I mean we are biased towards the familiar and therefore we can experience a new application as "wrong-headed" when it turns out not to work the same way as the one we already know. This is equally true, I suspect, for Access developers trying to learn another development tool.
Start out with a grounding in the principles of Normalization, which is the method by which properly designed relational tables are developed. And keep an open mind about coding VBA and using expressions. Many things are done for similar goals, but the specific functions and functions should not be duplicated rotely.