I have some automated procedures that send out reports via email. This procedure has worked well for over 15 years. Suddenly last week, I started getting this error: 2302 Microsoft Access can't save the output data to the file you've selected. The procedure creates a report.PDF temp file that used to go away after the procedure ran. Now it appears the file has some kind of lock on it and it can't be deleted. If the server or PC that Access is running on is rebooted, the file disappears and the procedure will run one time but the next time the procedure runs, it gives the error. Anyone have any ideas how to fix this? I can't reboot the server after every procedure and I don't know what has changed. I thought it might be related to the windows user profile so deleted the profile and recreated it but still got the error.
Doyce Winberry
Manufacturing
Manager Systems
XPO
2001 Benton Street
Searcy, AR 72143 USA
O: +1 501-207-5973 M: +1 501-207-2269
Selasa, 10 September 2024
Re: [MSAccessProfessionals] Error 2302
Check to see what MS Windows and/or office service patched have been recently applied - especially those related to the filesystem and/or security.
They would be the first candidates to be reversed to see if they are the root cause of the issue. Long-term stable running code doesn't start throwing errors and weird behavior out of the blue. Recent updates are your most likely culprits - MS seems to have forgotten about anything resembling real, actual QA testing anymore. Instead, they are relying too much on their automated testing suites that don't actually exercise a BUNCH of APIs that application typically DO use - and in ways that the testing scripts don't use them.
This has become the new "same-old; same-old" from Microsoft anymore.
On 09/10/2024 2:42 PM EDT Doyce Winberry via groups.io <doyce.winberry=xpo.com@groups.io> wrote:
Langganan:
Posting Komentar (Atom)
Tidak ada komentar:
Posting Komentar