She
loves shoes, as most women seem to do. How many pairs do they need!
Access works reasonably well as a desktop, single user, database. It's better than Excel for that purpose, but how many people use Excel as a database? Lots - that I've come across anyway. When you start adding multi-user capabilities, it breaks.
It's worse when using Access as a client for other, proper, databases

, unless the queries are set up to "pass through". I had a problem once, which was quite amusing, like this:
User started a query, it was accessing Oracle, and was attempting to scan a LNG data type for a particular piece of text. This is actually forbidden with LONGs in Oracle. The query joined three very large tables, in addition.
So, Access decided that it knew Oracle doesn't like doing scans of LONGs, and thought that it would pull the data up onto the desktop, convert the LONG to an Access TEXT data type, and scan that. The query never returned so the user shutdown access with the X button, and went on holiday for two weeks.
Access, carried on! It was attempting to pull the three huge tables back, but had completely dropped the join clauses and ended up in a Cartesian join of three mega tables. Oracle ran out of sort space when it got to the bit where it attempted to sort something like 270 trillion rows of data. Oops!
We advised the user not to be so silly in future and to always use a pass through. We (the DBA Team) did some testing to make sure that it was reproducible, it was. When Access doesn't pass through, it attempts to do stuff forbidden in the database, it will drop join clauses and Cartesian join everything to everything else.
I don't "do" SQL Server. Ever. Not after the first few times. I know a very large UK bank that still uses it, and still encounters massive problems.
Good luck with your problem, I hope you get it fixed. Is the SA password SA by any chance?
Cheers,
Norm.