Jim
If it used to work and now doesn’t you can blame it on a patch. Perhaps, MS decided to tighten up its sloppy VBA.
Arnelito might have hit on the cause if the error code is to be believed. First thing I would do is check to see if any other processes are running when this code fires. If there aren’t any then go through your code to make sure you set all objects to Nothing when you are through with them as you did with:
Set objFSO = Nothing
I know this must be frustrating to you. Code that suddenly stops working is very difficult to debug.
One more thing…It might be a sign of code page corruption. Importing everything into a new, blank database might help.
Regards,
Bill Mosca
From: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io> On Behalf Of Jim Wagner
Sent: Wednesday, January 12, 2022 7:49 AM
To: MSAccessProfessionals@groups.io
Subject: Re: [MSAccessProfessionals] Error 70 permission denied
Arnelito,
I do not understand that if this has worked for at least a year, why would it all of a sudden do this?
Jim Wagner
From: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io> on behalf of Arnelito Puzon <agpuzon@gmail.com>
Sent: Wednesday, January 12, 2022 3:30 AM
To: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io>
Subject: Re: [MSAccessProfessionals] Error 70 permission denied
Error 70, means the file is in use. meaning some process is using the file.
--
Arnelito G. Puzon
Tidak ada komentar:
Posting Komentar