Workbook.Close closes the wrong Workbook?

[bsabiston]

I've got some code that opens a workbook, does some work, and then closes it. The code is running from another workbook. This works unless both workbooks are already open when I run the Sub. Then it closes the wrong workbook - it closes the one that is running the sub.
Anyone know why that would happen?

Please Login or Register  to view this content.

So, it it supposed to open 'export.xls', run a function, and then close it. And it does that UNLESS 'export.xls' is already open. In that case, it closes my oMain worksheet.
Why does it do that?

Thanks!

[unit285]

Try

Please Login or Register  to view this content.

[6StringJazzer]

I set up a test. The only difference was that my machine does not have an environment variable called APP_PATH. But otherwise I ran this code with both files open and it correctly closed the export one.

The fact that you qualify the call to Close with oExporter should guarantee that the correct file is closed. I would put a checkpoint on that line and determine what oExporter.Name is before the Close is executed and see what comes up.

[bsabiston]

Ha - yes, it is the same name!

I'm working on an Excel that I did not create, and I know there is some kind of link between that 'export.xls' file and the main .xlsm file that is running the sub.
So, after that call to Workbooks.Open, oExporter.Name is the name of my main .xlsm file, not 'export.xls' as I would have expected.

Can two workbooks have the same name, even if the filenames are different?

Hmm apparently this is a known issue with Excel:
https://stackoverflow.com/questions/...e-wrong-object

The 'accepted answer' is to quit Excel and relaunch, but that didn't work for me. The second answer does work.

Please Login or Register  to view this content.