Jim Has a Question
Usually I recommend people to the Newsgroups or a forum for Excel questions, however it looks like Jim didn’t have any luck there, so I’ll post the question here for him (also because I was delayed in responding).
Jim, I don’t have any experience with your issue, hopefully a passerby might. And the question:
“My application calls for Application.WindowState=xlMaximized at Open. For some users, however, it does not execute. Moreover, when they run procedures that Unprotect then Protect the WB (to make some forms visible and hide some) Excel quits. I wrote the application in Excel 97 and also use it in Excel XP, but I have never encountered this problem myself. Yet, for the 5% of my users that do encounter it, it’s frustrating. Is there a work around procedure I can write? Or a third-party utility I can recommend to fix their problem? Do you have any idea why they might encounter this problem? Please help me get a handle on this problem if you can. Thank you in advance.”
Hi.
I don’t know what the problem is but it sounds similar to something I get from time to time.
Sometimes my users (running Excel XP) open a workbook and the window is not maximised. Fine.
They’ll go to click the maximise button and nothing happens. The button looks like it should work. It’s not ghosted, it looks fine – it just doesn’t work.
It’s not until they resize the window, even a little bit, that the maximise button is re-enabled. Then they can maximise.
What I suggest is using something like:
With Application
On Error Resume Next
.Width = .Width + 1
.Width = .Width – 1
.WindowState = xlMaximized
End With
this does not really help, but maybe you could audit there PC and see it there is a comman “thing” with each of them – google sreach or somthing? –
not very useful really, sorry