New Member
Excel Expert
November 22, 2023
Are these two Excel (365) issues related?
A) Some of my workbooks use Power Query to build a Table used purely for reference from another workbook, All-Stations.xlsx.
If I need to update All-Stations.xlsx, first I close any workbooks referencing it and then open it, amend it and save.
Often the save won’t work and Excel insists on saving it with a name it specifies, like AB012345. I can then rename All-Stations.xlsx as All-Stations-OLD.xlsx and rename AB012345 as All-Stations.xlsx, then all is OK.
But why must I do this?
B) Sometimes a workbook named PERSONAL.XLSB pops up. It appears to be empty, I dismiss (X) it.
I have no idea why it is on my PC but understand it is related to macros (which I don’t use) so have used View/Macros/View Macros and All Open Workbooks to list any. There never are any listed. If I delete it, it is rebuilt when I next open a workbook.
The following users say thank you to Keith Ward for this useful post:
Hans HallebeekTrusted Members
October 17, 2018
Nothing to do with 365, at least not visibly, I do not use 365 and have 2021 installed and have been using it since it exists.
This just started happening about 2-3 weeks ago and the files that I normally use just close when I confirm that I want to end a session (macro's) and then no questions asked and if there are no more workbooks open the Excel will quit or the file will just close.
I will have to check once again if there are other Excel instances open.
Trusted Members
October 17, 2018
I finaly found the reason, there was an AddIn loaded that itself loaded 2 more.
One of these does something that makes Excel 'think' changes have been made and therefore ignores my code that tells it that it's okay to close without saving.
Since they're not mine and I cannot look into the VBA code I'm going to contact the person for whom I'm testing them and see if het can tell me, and, I am offering a suggestion to add a button to the QAT wicth which I can choose to load and unload this AddIn.
I don't need it all the time.
Thanks for having looked and I unnecessarily blamed MicroSoft for behind-the-scenes modifications, oops!
1 Guest(s)