Read-Only Personal Macro Workbook
yg_be Posted messages 23437 Registration date Status Contributeur Last intervention -
Hello,
I'm questioning an anomaly with the personal macro workbook that I installed on a colleague's computer.
As soon as he opens any Excel file, the window "The file Personal.xlsb is read-only" appears.
I can't understand where the issue is coming from because I performed the same operation on 3 other computers without any problem. Now I'm deleting the personal.xlsb file, starting from scratch, and the problem comes back...
I tried going into Windows on the personal.xlsb file and there are indeed read and write permissions.
If anyone has a lead?
2 réponses
Hello,
I believe I can guess that you are installing a personal.xlsb file exported from your computer onto other computers.
Is that correct?
I don't think that's a good practice.
Excel has (or had) two modes of operation:
- one mode where each file opened in a different instance of Excel
- one mode where all files opened in the same instance
Maybe one of the computers is running in the first mode, which is causing multiple openings of the xlsb?
Or it might be that there is a lingering instance of Excel keeping the xlsb file open?
Hello,
No, actually I'm recording a personal workbook macro so that the Personal.xlsb file is created automatically.
I'm not exporting the macro I've created on my own PC; I copy it into a txt file that I send to the person I want to share it with.
I copy and paste the code contained in the txt file into the already existing personal.xlsb.
I feel like it's as if the personal.xlsb file is triggered to open with every new Excel file that opens. I need to get confirmation on this, but it seems to me that the anomaly only appears when opening the first Excel file. Once it's opened for the first time, it seems like it behaves as if it were being opened from another session and that we are already writing on it.
I also need to explore another possibility that the session used for remote work isn't responsible for the problem...
A priori, there is no reason to modify the file personal.xlsb like that on any computer. Why are you doing this?
I develop the macro on my PC and once it's ready, I just have to copy and paste the code inside. I could also import the module but I admit that I complicate things for myself. But in itself, I don't think that's the source of the problem.
Why not put the macro in a "normal" Excel workbook? Why mess with "personal.xlsb"?
We extract from a third-party software that generates a tmp****.xls file with a random name.
The simplest solution for me was to use a personal macro that applies to any file regardless of its name and can be launched directly via a shortcut in the Excel ribbon.