Is this app trying to send a file through "New Outlook" ? Because so far as we have heard, New Outlook is not compatible with Component Object Model (COM) programming that would occur if you used an Outlook Application Object. It is unclear exactly what the New Outlook will or won't do for certain other non-App-Object functions.
You should note that it is an "Exception" breakpoint, which means that the CPU's hardware got involved
during the attempt to execute some instruction, probably a hard-coded "BREAKPOINT" instruction. This differs from errors such as "data type mismatch" or "missing operator" where software checks for initial conditions
before executing something. Several different internal errors can be triggered this way but they have different error codes. For instance, a memory reference to a non-existent location is error 0x80000005, not ...0003. This ...00005 error depends on the way that Windows (and DOS before it) implemented breakpoints. It involved insertion of a breakpoint instruction in place of a given instruction, which caused a particular kind of CPU trap to be triggered, interrupting normal program flow. What else happens after that gets kind of complex, but the idea is that there is a specific instruction involved.
This particular error
could also be caused by a corrupted VBA module, so a decompile/recompile sequence
might help. No promises, though.
"Steps To Decompile Your MS Access-Database1)On a Windows system go to Start and type ‘msaccess.exe /decompile ‘in the Run command line. Here msaccess.exe...
techcommunity.microsoft.com
However, if the problem is actually that you are suddenly and unexpectedly using New Outlook, the only solution is to somehow revert to Old ('scuse me... Traditional) Outlook. Since I DON'T have New Outlook, I can't tell you much more than that and must defer to my colleagues for how to accomplish that switch-back and how to detect which Outlook you are running.
