I have an issue that is maybe so narrow no one else has seen it but I'll throw it out there ... I inherited some nighlty processes that are run by batch file, a bunch of msaccess.exe /x which run some updates, and data tranfers. They also email some reports via DoCmd.SendObject; not a great process but it worked fine until a couple weeks ago. I RDP to the machine that runs this as needed. But now, the DoCmd.SendObject will not run unless someone is connected. When the process gets to the SendObject, it just sits there, not running, no errors, no messages. As soon as I connect, everything starts to go. Security patch issue maybe? DoCmd.Send semi-deprecated? When I change the reports instead to go via Outlook.Application, those run fine. I'll keep doing that, but there are dozens. Any ideas? Steve Conklin
__._,_.___
Posted by: Steve Conklin <stephenmconklin@hotmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (11) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar