In table properties, there is an option called “Allow row to break across pages”. Is there a way in Aspose.Words for Java to explicitly set or unset this table property?
I’m actually trying to solve a problem I’m having related to this property. I have a table in the middle of a document. In this table, the property is not checked. Using Aspose.Words, I delete some nodes (paragraphs) around this table, some before and some after. I do not touch the table itself in any way. Then I save the document. When I open the saved document in Word and look at the table properties, I see that the property is checked, which is not what I want. I want the table property to retain its original setting.
Might deleting other nodes around the table indirectly affect this property? I wouldn’t think so. I assume that this property is maintained within the table itself, right? Could it be a preference setting or option somewhere in my Word itself that affects how this property shows up?
I would welcome any ideas or suggestions you might have.
Concerning the arbitrary change of this setting during processing of the document by Aspose.Words please attach the document and code snippet that will allow us to reproduce this problem. Once reproduced we can go ahead and fix it.
I’m seeing the same strange behavior. I’m attaching a document created with Word 2000. It has a table with the “Allow row to break across pages” property set to false. (You can open this document with Word 2003 and verify that the property is set to false).
But when I open the document with Aspose.Words Java edition and check the property it has changed to true.
This is a problem because some of the rows in this table may span several pages so I need to be able to preserve the original value of this property.
Thanks for additional info. I have reproduced the problem. It exists in both .NET and Java version. I have logged it to our defect base as issue #1406. We will try to fix it as soon as possible.
And yes, there already have been some problems with this property in some tables but we fixed them.