| Home |
| Search |
| Today's Posts |
|
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Feedback To The Group
I've struggled with my application appearing wallet-sized, even after
calling Application.WindowState=xlMaximized. Moreover, Excel would quit on a later call of the same the same procedure. For all you to know future reference, the problem was solved by deleting the call. Seemingly, Application.WindowState calls on Excel, but if there's an issue on the user's computer (e.g., something that conflicts), the call isn't made, and Excel trips out. Hope it helps equip you. Jim Kobzeff |
|
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
Feedback To The Group
Thank you. Sounds like a bug in the Windows O/S.
"JK" wrote: I've struggled with my application appearing wallet-sized, even after calling Application.WindowState=xlMaximized. Moreover, Excel would quit on a later call of the same the same procedure. For all you to know future reference, the problem was solved by deleting the call. Seemingly, Application.WindowState calls on Excel, but if there's an issue on the user's computer (e.g., something that conflicts), the call isn't made, and Excel trips out. Hope it helps equip you. Jim Kobzeff |
| Reply |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| Feedback Statistics? | Excel Discussion (Misc queries) | |||
| Customer Feedback chart | Charts and Charting in Excel | |||
| Template feedback | Setting up and Configuration of Excel | |||
| Hyperlink to provide feedback | Excel Discussion (Misc queries) | |||
| VBA programmer feedback | Excel Programming | |||
Linear Mode
