Clicking a tab opens it in a new window

[tmelch]

Version: 2008
Operating System: Mac OS X 10.4 (Tiger)
Processor: Intel

Why when I click on a tab in a workbook does it open in another window? Very irritating because after working in a worksheet a while I end up with 30 or 40 open windows that I have to close and click "Don't Save" on. I see in another closed thread where resaving in a previous version fixes the problem but that is not acceptable. We are also running Excel 2008 on Leopard and it does not do this. Is this a compatibility issue with Tiger?

 

[CyberTaz]

It certainly isn't a compatibility issue -- you'd find more than one
archived post on it if it were I've run 2008 on Tiger since the Beta
testing & have never seen this happen.

Since you haven't specified your installation update levels the first things
I'd suggest are that you:

1- Update Tiger to 10.4.11 using the COMBO updater from the Apple Downloads
site (even if you're already updated to that version via Software Update).

2- Make sure Office 2008 is fully udpated (12.2.1 is the most current).

3- Repair disk permissions (just as a matter of routine) after any updating
& restart the Mac.

4- If the problem persists after that, log in while holding Shift. If that
cures it there is some other app or utility that is interfering with the OS
X windowing engine... It's just a matter of finding out what that is.

Come back if none of the above resolve it.

 

[tmelch]

Regarding my system, I AM running dual monitors on a MacBook Pro. I just figured out that if the spreadsheet is open on the main screen it does not happen. When it is open on the other screen, it happens, but not with every tab.

I'm on Tiger 10.4.11.Excel 12.1.9, will upgrade, run Disk Utility, and try the Shift trick. But the dual monitor is perhaps the reason this doesn't come up. Bet the other users that had the problem were running dual monitors.

 

[CyberTaz]

I think you're right on all counts Unfortunately, I don't believe the
matter has been resolved. My understanding is that this may be one of those
"MS can't fix it til Apple changes this which won't work until MS does
such&such..." ad infinitum.

I'd still strongly recommend the updates be done.