Fix the "System Resource Exceeded" error that requires Processor Affinity be set to 0.
We have a number of users at work who regularly report, when using Access 2016, that they get a "System Resource Exceeded" error when running certain queries. It is intermittent, but happens frequently. Didn't used to happen on Office 2010, or under Windows 7. Happens regularly under Office 2016 under Windows 10.
Multiple threads online point to the current "workaround" being to set Processor Affinity to 0, rather than utilizing all cores of the process. This seems like a shitty solution, and it would be better if the underlying issue(s) with using multi-core processor(s) would be fixed, so the workaround was no longer necessary. This bug dates back many years and has apparently never been properly addressed by Microsoft.
Basically Google "System Resource Exceeded" + "Affinity"...