Using version 4.9.1.0, there are several problems with XLSX files. I've attached an XLS and XLSX made identically. The XLS file is fine. The XLSX files gives errors about unreadable content when loading into Excel 2007. It complains both about a named range and a formula.
There is also a problem with comment formatting. You can see that in the XLS it correctly autofits the comment box, whereas in the XLSX it does not.
Finally, it was my understanding that 4.9.1.0 allows more than 65K rows and 256 columns to be fully utilized in formulas. On our initial experiments, we find this does not work, and that we get spurious "circular reference" errors due to truncation of cell references to higher-numbered rows. Unfortunately, the XLSX file that exhibits this problem is rather large. How would you like us to help you debug this issue?
Regards,
--Howard
Hi,
We have logged your issues into our tracking system and assigned them a ticket:
CELLSNET-17384.
We will soon look into your mentioned issues and figure them out. Once the issues are sorted out, we will provide the fix.
Thank you.
Hi,
Please try the attached version v4.9.1.8.
We have fixed your mentioned issue.
Thank you.
The issues you have found earlier (filed as 17384) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
While trying to keep the API as straightforward and clear as possible, we have decided to recognize and honor the common development practices of the platform; we have re-arranged API Structure/ Namespaces.
With this release, we have reorganized the API classes for Aspose.Cells component. This change has some major aspects that we follow. We have added new namespaces. The entire API (classes, interfaces, enumerations, structures etc.) were previously located in the Aspose.Cells namespace. Now, certain sets of API have been moved to their relative namespaces, which make the relationship of classes (with their members) and namespaces clear and simplified. It is to be noted here, we have not renamed existing API (classes, enumerations etc.) but, I am afraid you still need to make certain adjustments in your existing projects accordingly.
For complete reference, please see the product's API Reference.