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"...

EdbMails provides an Office 365 Tenant Migration utility to migrate mailboxes between O365 tenants. An intuitive, secure, and scalable solution for migrating Office 365 mailboxes. It performs the rapid data migration with privacy and control. EdbMails supports the migration of mailboxes, archive mailboxes, public folders, shared mailboxes, Office 365 Groups, Office 365 teams, SharePoint sites, and OneDrive for Businesses.
Office 365 migration Features
· Migrates mailboxes, Archive mailboxes, Public Folders, and Shared mailboxes
· It Migrates Emails, Folders, Drafts, Sent Items, Deleted Items, Inbox, and Junk folders, etc., to your target server.
· Supports Office 365 mailbox to Exchange server 2007, 2010, 2013, 2016, and 2019 migration
· Supports incremental migration: Only the newly added items are migrated to your target server on consecutive migrations, avoiding duplicate items migration.
· Automatically maps the source and target mailboxes for the migration operation. Also, it allows you to map the target mailboxes manually.
· Allows to apply 'subject,' 'sent date,' 'received date,' 'attachment name,' 'from' and 'to' address-based filters for specific data migration.
No Outlook dependency: Without installing Outlook on your computer, perform migrations from one Office 365 tenant to another, Office 365 to Exchange Server, and Office 365 to PST.

Try “Free Trial version’ to verify the functionality of the software where you can perform mailbox,public folder, and archive mailbox, shared mailbox migration.

To Know More Visit: https://www.edbmails.com/pages/office-365-migration-tool.html

For MS Access textboxes on Forms that handle dates you can set the textbox to allow the user to optionally use a built-in DatePicker. However the DatePicker returns the date in a format set by the Windows system (e.g. as Set by Control Panel > Region > |Formats| > [Additional Settings ...] > |Date| > Short Date:)

If you use a unorthodox windows system date format, e.g. "yyyy-/MM-MMM/-dd, ddd" returning "2021/-05-May/-18, Wed" then this can be undesirably returned by the DatePicker.

Instead the DatePicker should return a date that honors any custom format set by in Format property of the Textbox control itself. E.g. If the developer sets an ISO8601 format "yyyy-mm-dd" in the Textbox format property then the DatePicker should return text like "2021-05-18".

For MS Access textboxes on Forms that handle dates you can set the textbox to allow the user to optionally use a built-in DatePicker. However the DatePicker returns the date in a format set by the Windows system (e.g. as Set by Control Panel > Region > |Formats| > [Additional Settings ...] > |Date| > Short Date:)

If you use a unorthodox windows system date format, e.g. "yyyy-/MM-MMM/-dd, ddd" returning "2021/-05-May/-18, Wed" then this can be undesirably returned by the DatePicker.

Instead the DatePicker should return a date that honors any custom format set by in Format property of the Textbox control itself. E.g. If the developer sets an ISO8601 format "yyyy-mm-dd" in the Textbox format property then the DatePicker should return text like "2021-05-18".

In order to add a Add-in (.mda) file into MS Access, the user has to be in the local admins group. Even if you are a domain admin, not having local admin rights won't work because your user profile changes when you open MS Access as Admin with other credentials.

Full Detail: In order to Install an Add-in library in MS Access 2016 (and at least the two prior versions) you have to open MS Access 'Run as Administrator', then do the install, then close and reopen as the standard user. If you are not in the local administrators group you must log off, login with admin rights, add the user into the local admins group, logout, login as user, run MS Access as Admin, install the add-in, remove the user from the local admins group, then logout and back in again to use it.

The simplest solution is to allow this whole process to be done by the regular user, as long as the appropriate settings are in the Trust Center. Could be anything; Add-in File in the Trusted Locations, Add-in File is a Trusted Document, Add-in File is Digitally Signed requirement stops install if not signed, but otherwise allow. I like the last one the best myself.