'PERSONAL.XLSB' is already open, cannot open 2 docs with same name - local / roaming

Question

{ Repost from http://www.ozgrid.com/forum/showthread.php?t=151529 }

Every time I start XL, I get the error message:

- A document with the name 'PERSONAL.XLSB' is already open. You cannot open two documents with the same name, even if the documents are in different folders. To open the second document, either close the document that is already open, or rename one of the documents.

I'm running Excel 2007 SP2 on Vista. ( Please don't post replies that involve changing either of those, no matter how passionate you may be about it!  )

I have found that the two files are located in:

• C:\Users\Critcho\AppData*Roaming*\Microsoft\Excel\XLSTART

and

• C:\Users\Critcho\AppData*Local*\Microsoft\Office\xlStart

In the past, I have deleted one of the files, and it has been regenerated without any action from me to request such.

I have also renamed one of the files to C:\Users\Critcho\AppData\Roaming\Microsoft\Excel\XLSTART\PERSONAL2.XLSB, but that didn't help.

So now I have 3 macro workbooks and still get the error each time I start XL. While it's not a critical error, it's an annoyance; but I'm more concerned about where all my macros are stored.

So.... how do I:

• Stop XL from regenerating these files
• more importantly -Merge all 3 versions back into one workbook so I don't loose any of the macros I have written (few hundred in there I'm guessing)

I only ever use the one login to this laptop, it's not like I'm joining a domain at work then using a homegroup at home or anything like that, I'm wondering what makes it pick between the local and roaming AppData sets.

Thanks for your help!

Cheers,

Critcho.

Answer 1

I would do some testing:

• move both xlsb's out of the folders they are in
• Open Excel, record a macro to the personal macro workbook, close Excel and save.

This gets you the current location.

• Rename the ones you copied so their names are unique, open them and copy their modules (the ones you want to keep) to the new one.

If this problem keeps pestering you, I would consider moving your code to a workbook with a special name (MyMacroBook :-)) and save that as an add-in you can install. Of course if you now record a macro, you'll have to remember to copy it to your new macro add-in, but it saves you the trouble of two personal's