Maximum number of columns

Aspose.Words Product Family
1

We are using Aspose word to programatically export the output of a table based report to a word document. What is the maximum number of columns that can be in the table created in the word document?

2

Hi there,


Thanks for your inquiry.

In Microsoft Word you can insert a table with up to 63 columns, that is the limit to the number of columns allowed in a Word document.

I have checked, and when a table is created using Aspose.Words with more than 63 columns the output document cannot be opened. I have logged a new issue for this to make sure we do something about this, either a warning or to fix such tables upon save. The issue ID is: WORDSNET-6352. We will keep you informed of any developments regarding this issue.

Thanks,
3

Thanks Adam for the quick response. Let us know when
you figure out a way to handle the scenario of more than 63 columns. We
have reports that will have more than 63 columns and would ideally like
to have the data from all the columns exported to word document. If it
cannot be done due to limitation of Microsoft word there should be a
graceful way to handle the scenario.



Thanks

4

Hi there,


Thanks for this additional information.

Most likely there is nothing we can do to actually solve the issue, as this is a limitation of the Word document. We will simply add validation to such documents so they are corrected on save and won’t cause any errors when opened and/or we will provide a warning through the IWarningCallback interface when this situation occurs.

It seems normally a table with 63 columns wouldn’t be properly visible in a normal word document because there are so many columns. Could you clarify exactly how your report looks like when generated? You can most likely work around this issue by creating a second table when your input data reaches over 63 pieces of information and place the data into the second table instead. Then you can place the tables side-by-side.

Please let me know if this is acceptable to you.

Thanks,
5

The issues you have found earlier (filed as WORDSNET-6352) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.