A family of Microsoft relational database management systems designed for ease of use.
Yes, it is hard to find info.
The setting applies when you have a linked table to SharePoint. In “most” cases this suggests a web published 2010 Application to SharePoint, but not always!
In Access 2010 you can publish the application as web based. This web publishing feature allows even standard VBA forms to be moved up to SharePoint. So these VBA forms publish to the SharePoint site, thus have VBA code, but ONLY on client computers with desktop Access (full or runtime) installed.
The key concept here is the table(s) used for that form can have data macros attached at the table level – and these tables and that data macro code run on SharePoint – not the client side.
Thus when updating data in a form, that “act” can cause a data macro to run on the server side (aka SharePoint). Such data macros are often slow to respond. So this option defaults to no, and it would allow you to go back to work while the data macro on SharePoint runs. However, if that data macro is totalling up some Invoice amount that you NEED in your code or form, then you don’t want to proceed until such time that code is finished. So you would set the option = yes to “wait” until that processing is done.
So the setting ONLY applies to SharePoint tables being used with Access. So the setting in most cases in the context of a published Access 2010 application, but also applies to non-web based and non-published Access applications that are using SharePoint tables.
I suppose the option should have been named “Wait for SharePoint processing”.
Regards,
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada