Two Dimensional Cell array of column without creating a named range

Hi Nausherwan,

Any updates on this front.

Thank You.
Kailas

Hi Kailas,

Thank you for your continuous support to figure out this issue. It is really a strange issue, according to the debug info; it seems there are some wrong styles set on the source Column objects. How did you create the source workbook? Do you have multi-threads application that maybe modifies the workbook concurrently? Here is another debug version, it can help us to get more info about the source workbook, but it takes time to trace the root cause of such issues.

Thank you for your help and patience.

Hi,

Thanks for your quick response.

Please find the attached debug messages.

Thank You.
Kailas

Hi nausherwan,

Any updates on this front.

Thank You.
Kailas


Hi,

Please send me the source code for the Copy worksheet method so that I can check it from my side.

Thank You.
Kailas

Hi Kailas,

Thank you for considering Aspose.

I am afraid the source code of copying worksheet or column will be of no help to trace the issue, because there are many other internal variables and methods of other objects being used by the copy method. By the debug info you sent to us, what we came to know is that there are some Columns(according to the output info, column IW-JP) in your source sheet using invalid style reference. We have built another debug version for tracing where such invalid styles are set to those columns. Hopefully it can get us closer to the root cause of the issue.

Thank you for your help and support to find out the issue,

Hi Nausherwan,


Please find the attached debug messages.

Appriciate a quick response as we are getting delayed due to this issue.

This issue is not occuring in the last Aspose Version 1.9.5.1 we were using.


Thank You.

Kailas

Hi Kailas,

Please use the attached debug version to get some more information regarding this issue.

Thank you for your help and understanding,

Hi,

Please find the attached debug messages.

Thank You.
Kailas

Hi,

Can you suggest a work around as an immediate fix so that we can continue with our testing cycle till you have a concrete solution in place? Out 40% system functionality is dependent on the reports that we are facing this problem in. Please advice.

Thanks & Regards,

Sandeep Bansi Jumani

Team Lead

Hi Kailas,

Thank you for considering Aspose.

We have found one possible reason for this issue. We think you must have reused a Workbook object after saving a workbook for further processing without re-instantiating it. Generally, after saving a Workbook (by Workbook.save(…)), many attributes in the Workbook object, such as styles, will be rearranged. This procedure may cause some attributes of the workbook object inconsistent for later use. The recommended and safe way to use a Workbook object is, after calling Workbook.save(…) method, if you need further processing on that workbook object, instantiate your object and reopen the source file to build a new Workbook object to replace the old one.

Any way, we have fixed the possible cause of your issue, please try this new fix and let us know whether your issue gets resolved.

Please see the following code sample for more clarity of the issue,

Your code maybe like:

Workbook workbookSrc = new Workbook();

workbookSrc.open("source.xls");

//here do some works with the workbookSrc object

workbookSrc.save("result.xls");

Workbook workbookNew = new Workbook();

//maybe there are some other work need to do with the Workbook, such as using its data, doing copy, ..., etc.

workbookNew.copy(workbookSrc);

the recommended code is:

Workbook workbookSrc = new Workbook();

workbookSrc.open("source.xls");


//here do some works with the workbookSrc object


workbookSrc.save("result.xls");

//Re-Instantiate the workbook object for further use

workbookSrc = new Workbook();

workbookSrc.open("source.xls");

Workbook workbookNew = new Workbook();

//maybe there are some other work need to do with the Workbook, such as using its data, doing copy, ..., etc.

workbookNew.copy(workbookSrc);

Thank you for your continuous help.

Hi nausherwan,

Thanks for your positive response.

Please provide a Non debug version of this jar.

Thanks for your quick supports.
Kailas

Hi Kailas,

Thank you for considering Aspose.

Please find the attached latest non-dubug fix.

Thank You & Best Regards,