When creating a workbook from scrath (no template) and opening the file
in Excel the opened window is really small. Is there any method to
control the width and height or would it be possible to increase the
I am not clear about your problem. Could you please post your generated file or a screenshot here to show your need?
See attached screenshot.
Is it possible you didn't close MS Excel correctly? Could you post a sample file here? I will try to open it in MS Excel to see what will happen. Thank you.
Here is a sample file generated.
It doesn't seem to a problem of generated file. Instead, it relates to your MS Excel. In my machine, the file is opened in maximized window.
Please maximize your file window in MS Excel then close Excel. Then please open the file again.
The issue is in fact related to Aspose. Of course there is no problem
when a window is maximized. A maximized window always takes up the
whole window. You can see the difference between Aspose and other apis
when you open files in non maximized mode. I have attached two
different files here. One is created by JExcelApi and the other is
created by Aspose. If you open both of these files in non maximized
mode, you will see the difference I am talking about. The Aspose window
is really tiny and the JExcelApi window is much larger. I have also
attached a screen shot of the two files opened in my excel to show you
what I mean.
I understand your need now. We will check this issue ASAP.
Please try this attached fix.
It works great. Thanks for your quick response.
I think I’m seeing the same issue in the .NET version – When an XLS file is opened that was generated by Aspose.Cells, the window is small, and not maximized. Is it possible that this is the same problem, and the fix hasn’t made it into the .NET version of Aspose.Cells?
Any help would be greatly appreciated. Thanks!
There should be no such issue in .NET version of Aspose.Cells, we could not find the issue. Kindly create a sample project, zip it and post it here with all the details to reproduce the issue, we will check it soon.