Forum Discussion
Running Macro Causes Reference File to Save somewhere else
I can't seem to replicate this error but it happens at least once a week. I open a file where I created some script. Does not matter if it is an older file or a newer one and I get the dreaded error ...
Hi heylookitsme
So you're running your macro and before your macro ends its procedure, someone opens your reference file as read only, what would happen to the rest of the procedure?
Can't say I follow what your asking. If I have a file open with Write access and I am running a procedure against it and someone opens the same Excel file as read-only, both would be two separate actions because the file is not a shared file. The reference file for each person resides on their C Drive in the Microsoft Library folders. One factor I have found that could be contributing to this error is Microsoft becomes extremely unstable when you have some large files open. Microsoft needs a built in procedure that calculates the processor and ram usage to determine if opening a file will cause the program to not run correctly and prevent the user from opening a new file until one is shut down. I would much rather be told I can't open another file then to open one and have strange behaviors occur that are not explainable.