Hi John,
Thank you for using our products and sharing the sample code with us. I tried using your code to test your issue but due to missing variables, I was unable to replicate the scenario at my end. However, to exactly replicate your issue at our end, we would appreciate, if you create a sample application and post here to show us the issue. This will help us to regenerate the issue and get the cause of the issue soon.
We apologize for your inconvenience.
Thanks & Regards,
Hi John,
Thanks for sharing the details. I tried using your code to test your issue using Aspose.Pdf v6.7 but unable to find any issue with the code of line highlighted RED in your code. The complete code and resultant PDF document is attached for your reference. However, kindly visit the documentation link Create Nested Table for more details and code snippet as per your requirement.
Please feel free to contact support in case you need any further assistance.
Thanks & Regards,
It doesn’t look like I can include attachments.
I am really at a loss here. I am trying to update my code to 6.7 and upgrade but I can’t get anywhere on this.
Hi John,
Thank you for your feedback, I am very sorry for the inconvenience caused due to this issue. However, please find attached sample source code and resultant PDF in which DefaultCellBorder is used with nested table only. Moreover, if you are facing any Evaluation Version issue, kindly visit Purchase Information for all details about licensing, even before purchasing the license, you may also request a 30 days temporary license for evaluating the product.
Please do let us know if you need any further assistance.
Thanks & Regards,
Through hours of trial and error I did find the problem that caused all of my nested tables to fail after I upgraded. I used “FitWidth” to set the width of my columns in my code. The nesting of tables does not work unless you use myTable.ColumnWidths = (“50 50”) to set the column widths.
Hi John,
You are absolutely right, I am very sorry for the inconvenience caused due to this issue. However, I would like to share with you that "FitWidth" property has been obsolete, kindly use the "Table.ColumnWidths" property instead of "Cell.FitWidth". We are really sorry for this inconvenience.
Thanks & Regards,