We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Some tables broken since update from to


First, i apologize because my english is very bad.
My current version: Aspose.Word.Net is

To simplify my problem:

I’m trying to create a table with 2 rows.
The first row must have 2 cells:
- 1 cell of 130 mm
- 1 cell of 60 mm
The second row must have 3 cells:
- 1 cell of 80 mm
- 1 cell of 60 mm
- 1 cell of 40 mm

I know that i exceeds a bit the default width of an A4, so, i have to use AutoFitBehavior.FixedColumnWidths to do this.

My main problem is that the first cell of the second row (80 mm) take automatically the width of the first cell of the first row (130 mm) when i use autofit to fixed column widths.

I get to do this when i use autofit to the windows (default behaviour) but then the widths of cells are not correct (not fixed).
My code (sample version):

Dim doctest As New Document()
Dim buildtest As New DocumentBuilder(doctest)
Dim tabtest As Table = buildtest.StartTable()

’ // tabtest.AutoFit(AutoFitBehavior.FixedColumnWidths) (already tested by placing it here)
buildtest.Writeln(“Row 1 Cell 1”)
buildtest.CellFormat.Width = ConvertUtil.MillimeterToPoint(130)

buildtest.Writeln(“Row 1 Cell 2”)
buildtest.CellFormat.Width = ConvertUtil.MillimeterToPoint(60)


buildtest.Writeln(“Row 2 Cell 1”)
buildtest.CellFormat.Width = ConvertUtil.MillimeterToPoint(80)

buildtest.Writeln(“Row 2 Cell 2”)
buildtest.CellFormat.Width = ConvertUtil.MillimeterToPoint(60)

buildtest.Writeln(“Row 2 Cell 3”)
buildtest.CellFormat.Width = ConvertUtil.MillimeterToPoint(40)


doctest.Save(System.IO.Path.GetTempPath & “ResultTest.pdf”)
doctest.Save(System.IO.Path.GetTempPath & “ResultTest.docx”)

See attachment for the result (output) of this code.
This code works without problem in version but not works in version

Can you help me?


Hi Ahmet,

Thanks for your inquiry. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-12611. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

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

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