Button:
The next time someone tries to promote Access as "easier" or even "cheaper" to use than the alternatives I'd be glad to quote you in support of my point of view, which is that it depends on the competence of the person doing the job and has nothing to do with Access as a product.
I learned the short form of this a long time ago in college: Artificial Intelligence cannot cope with natural stupidity.
Question: Is Access a database? No, it is a database processing tool. We don't have the same level of confusion over whether Word is a document or Excel is a spreadsheet or PowerPoint is a slide show or Outlook is a mail message. I attribute this to simply a careless approach to describing the product.
Let me ask the question another way that might help clarify the situation: Does Access contain enough features that one could base a generic college or trade-school course on databases using Access as the supporting tool? I think there that the answer is a resounding YES.
Access supports:
Tables with multiple fields and multiple data types and with indexes for operation optimization, including synthetic/autoincrement keys, compound keys, and multiple indexes.
Relationships between tables to support relational integrity (and also to support the design code that can read the relationships and act accordingly.)
Queries with SQL compatibility including WHERE and ORDER BY clauses, membership (IN) clauses, sub-queries, and JOIN and UNION operations.
Forms and reports with bound and unbound controls of many different types with events to allow traps and triggers to be tested/executed.
Sequencers (Macros) that allow us to stage multiple elementary operations into a longer command flow.
The ability to code various sequences of procedural language (VBA) instructions as one of the possible elements for events or macros.
The ability to link multiple tables together. The ability to manipulate objects in other formats. The ability to manipulate low-level properties of its own objects.
In summary, if I wanted to teach a course in the care and feeding of a true database (whatever that means), MS Access has all I would ever need. By that standard, Access is a perfectly reasonable tool.
There are some nay-sayers among us, and I have to admit that when MS dropped the older security model I wasn't happy. The new security model doesn't help me one bit. But I will report also that a comment in passing gave the wrong answer. There are a few database-oriented applications at my U.S. Navy site that use Access as the Front-End. I think they use an SQL Server Back-End. But I know that they don't have a problem with the capacity of the database as a whole. The biggest database of that group has well over 200 users who pound on it during the day shift, usually without major issues. So anyone who thinks that Access is "not good enough for government work," please be advised otherwise.