Agreed, provided the coding/sql statements you use are handled correctly. Far too often, Access is blamed for not supporting decent workloads, when it is often the fault of the code accessing the database for doing things like not opening connections late/closing them early or keeping rows locked through suboptimal/poorly written queries.
Access is probably one of the least forgiving in terms of adjusting for poorly written code/queries. It does GREAT with what you give it, but if what you give it garbage, then your results/performance are going to be the same.
Technical answers are yes. Real world answers are “you probably shouldn’t do that.”
I’d also argue for something of that scale, you are going to want some features which access can’t handle–like triggers, transactions and online backups.