I am looking for is a way to interract with Outlook from the code in the Word document that ensures that Outlook is ready to execute the next instruction, thereby avoiding the crash. Whatever time I choose it would still be possible for it to take longer! Also I am hoping to extend some of the functionality and would need to understand whether this will cause further problems. This is far from ideal as I can't reproduce the error and so optimizing the waiting time is difficult. This appears to have mostly prevented this problem, but I can't be completely sure. I have been able to implement a quick fix: įor instance I can add a short pause (1000 milliseconds, for instance) before the next email message is created.
The fact that I have been unable to reproduce the error might suggest that their particular setup is slower than mine? The crash seems to be occurring at the point where the next email message is being created, suggesting that the '.Send' is happening too slowly. Eventually this causes an instruction to be passed to Outlook while it is still executing the previous instruction, and this causes the crash.
My best guess is that the code is executing too quickly for my colleagues' Outlook application to keep up. I have not been able to reproduce this error although have seen it over a screen-share. Some people, after a few emails have been sent, get an error message and are directed to debug/end. If you ignore my question and suggest another method please consider this first! I am aware that other tools (paid or otherwise) exist to do this and that a macro-enabled document is a bit of a bodge. There are a specific set of requirements to my use-case that mean we've had to go down this route. It interacts with Outlook (which must already be open) to send email where the content of the Word document has been pasted into the message. I've a macro-enabled Word document to provide mail merge functionality (attachments, delayed delivery, etc).
0 kommentar(er)
