J
Jeremy
I have a docmd.transferspreadsheet procedure which was
working just fine. Then, it was run one day and the
computer froze (stuck on hourglass). So, I ctr+alt+del
and ended the MS Access program (which was 'not
responding'). Now, the docmd.transferspreadsheet
procedure does not work. I get run-time error #
3161 "Could not decrypt file". The error occurs on the
docmd.transferspreadsheet line. I didn't change anything
in the procedure or the file.
1. Does anybody know what to do about this error?
2. Is a ctr+alt+del what you are supposed to do to stop a
procedure which has hung up your computer? Is their a
better practice that prevents things like this from
happening?
Any help is greatly appreciated.
Jeremy
working just fine. Then, it was run one day and the
computer froze (stuck on hourglass). So, I ctr+alt+del
and ended the MS Access program (which was 'not
responding'). Now, the docmd.transferspreadsheet
procedure does not work. I get run-time error #
3161 "Could not decrypt file". The error occurs on the
docmd.transferspreadsheet line. I didn't change anything
in the procedure or the file.
1. Does anybody know what to do about this error?
2. Is a ctr+alt+del what you are supposed to do to stop a
procedure which has hung up your computer? Is their a
better practice that prevents things like this from
happening?
Any help is greatly appreciated.
Jeremy