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

Free Support Forum - aspose.com

Empty cells in SQL Reporting Services table are set to the font Times New Roman 1pt in MS Word

Aspose.Words Product Family
#1

I have been informed of this issue in Aspose for Words exporting from SQL Reporting Services…
I have a few reports that use SQL Reporting Services table tools. Some of the cells are left empty on purpose so that the users can enter data into those cells. The font on these empty cells are set to the same as the other cells in the table (in this example Arial 10 pt).
When the report is exported to MS Word, the font for the empty cells is changed to Times New Roman 1 pt. The users can change the font for the time being, but I wanted to report the issue in hopes it would be resolved.
I just recently down loaded Aspose.Word 3.2, and the error still occurs on this version as well.
Let me know if you need any further information.
Thank you,
T.J.

#2

Hi

Thanks for your inquiry. Could you please attach your rdl report and rdl.data file here for testing. We will check the issue and provide you more information.
Best regards.

#3

Alexey,
Thank you for the response.
I have attached the .rdl file, and a text file that is the text to create a Stored Procedure that will duplicate the error.
If you use this stored procedure as the data source, and export the report to MS Word, the first column of the first row (under “Case Information”) is an empty cell. The font is set to Arial 10, and even has a field for the data source, but since the cell is empty for this record, the MS Word changes the font from Arial 10 to Times New Roman 1.
If you need another example or any further information, let me know.
Thank you,
T.J. Bernard

#4

Hi

Thank you for additional information. I logged your request. You will be notified as soon as the issue is resolved.
Best regards.

#5

Hey, is this issue fixed? I have the same problem.

Regards, Fredrik Danielsen

#6

Hi

Thanks for your request. Unfortunately, the issue is still unresolved. You will be notified as soon as it is resolved.

Best regards,

#7

I have just fixed this issue. Please expect an official hotfix on Monday.
Thank you for waiting.

#8

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

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

#9

Hey, my problem is in Aspose Words for JasperReports (exporter). And the issue is still there, and no update.

Regards, Fredrik Danielsen