The existing email mechanics for sending emails to create/update data are nifty, but problematic.

1) they are so limited in terms of automatically enabling complex data handling and customized business rules - especially if attempting to inter-operate with other enterprise-level systems, like SAP or Dynamics as the final data repository. For example... wanting email approval of a work order or PO...the updates to the enterprise systems will require significant coding and implementation of business rules specific to the organization, but the email handling itself is relatively trivial.

2) the lack of ANY API accessibility in the email send/reply process, especially in the realm of error handling, is especially problematic. How can workflow be tracked properly when errors are encountered - especially when the entire process is governed ONLY by a manual UI wizard with no means of recording process-control results automatically? If we had APIs that interacted with the wizards (even if only in a read-only fashion, then we could automate some process control/tracking, and perhaps implement sufficient complex downstream data update procedures when applicable.

With NO API visibility into the email/update process at all, we are left with only manual processes, requiring user intervention - or complete abandonment of MS-Access as a solution all together.