Jim: thanks for your reply.

You suggested: "As a workaround can your code close Personal before
opening the other workbook"

I do not know what this means. Please clarify. Approaches I have
considered:

1. disabling the execution of any macros in A.xls or Personal.xls
That is what I was trying to do with EnableEvents

2. programmatically mod the code lines in Personal.xls that call the
problem-creating procedure before I open A.xls and then restoring the
code after I close A.xls I know how to do that, it just seems ugly.

3. programmatically move Personal.xls to another folder before opening
A.xls and then moving it back after I close A.xls Also ugly

4. bypassing the calls in Personal!Workbook_Open that create the
problem by testing what other workbooks are open. Unfortunately,
Personal.xls opens before anything else so the only WB it can see is
itself

Thanks

MWE


---
Message posted from http://www.ExcelForum.com/