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

Free Support Forum - aspose.com

Table Broken issue

<!–[if gte mso 10]> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tableau Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;}



We have some difficulties with tables and row breaks on page breaks in C#.

You can see the scheme of the table we created (it works fine) on the table1.jpg file attachaed. Each cell contains a nested table with a header and a content.

The 2x2 cell is totally filled with a picture (so a nested table with a header and a picture for content).

When we add this table to the end of our document, here is what happens: the picture is too huge to fit in the first page (cf table_prob.jpg). The red line is the page break.

The table attributes are set as IsRowBroken = false ; IsBroken = true ;

We expect the table to behave like in the table_whatwewant.jpg file.

We already tried image positioning attributes, IsKeptWithNext attributes, and IsBroken attributes, and many other things.

Is there any way to do this automatically, without calculating successively each first page element height, adding it together, and inserting a page break manually at the right location?

Thank you

Hi Anouck,

Thanks for using our products and sorry for delay in response.

Can you please share the code snippet so that we can test the scenario at our end. We apologize for your inconvenience.

It’s pretty difficult for us to do that, cause we have to write another sample code just for you (all our work is dynamical and depends on our database). Can’t you try to reproduce it yourself?

Hi Anouck,

We will try our level best to replicate this issue at our end and will keep you updated on the status of correction. Please be patient and spare us little time. We are sorry for the delay and inconvenience.

Thank you very much. If we have time to spend on this, we will do a sample code, but we are really busy right now.


We had time to make the sample code finally. But by doing this we found other issues. We attached to this message the sample. You should at first launch the AsposeSample3 cause this is the one that summarize the case we have in our release version.
As you can see when you launch it there are the following issues :
- the image should be with the header in the second page as showed at the beginning of this topic (here’s our main issue, the others may be linked but are not as important as this one)
- the bottom margin between each nested table should be gray as you can see at the last line
- when we applied a top margin to the footer, it appears as a bottom margin !

AsposeSample1 and 2 showed the two steps by which we passed before having this one.
In the first one you can see that without nested table or content, the middle cell is broken between the two pages and in the second one you can see the same issue with an image as a content.

Please, help us :slight_smile:

Hi Anouck,

Thanks for sharing the code snippet.
<span style=“font-size:10.0pt;font-family:“Arial”,“sans-serif””>

have tested the scenario and I am able to reproduce the table break issue. For the
sake of correction, I have logged it in our issue tracking system as <span style=“font-family:“Arial”,“sans-serif””>PDFNEWNET-30405. We
will investigate this issue in details and will keep you updated on the status
of a correction.<span style=“font-size:10.0pt;font-family:“Arial”,“sans-serif””><span style=“font-size:10.0pt;font-family:“Arial”,“sans-serif””>

apologize for your inconvenience.

The issues you have found earlier (filed as 30405) have been fixed in this update.

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

I downloaded the new version and check if it worked, and it didn’t. With exactly the same sample of code I still have the same problem. Can you please look at it again.



I’m still waiting for an answer… Our products using Aspose will be released in february and it’s been already two months…

Up! Could you at least tell me if the issue fix is underway ?

Hi Anouk,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

First of all, please accept our apologies for replying you late.

I have checked your issue with the latest version of Aspose.Pdf for .NET v6.7 and the issue still exists. I have reopened your issue and asked the development team to look into this issue on a high priority. As soon as I get a response, I will update you via this forum thread.

Sorry for the inconvenience,

Thanks for your patience. Please note that the issues you have found earlier (filed as PDFNEWNET-30405) have been fixed in this update.

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