Hi,
Are there any restrictions about the maximum size of an RTF control?
I have generated a RTF content using the SalRTF-Commands of an RTF control and tried to print the content by report builder. At page 13 the content is cutted in the middle of a word, and on preview the pages 14 and 15 are empty, on printing page 14 and 15 are showing the beginning of the RTF content.
See the example.
RTF control restrictions
RTF control restrictions
You do not have the required permissions to view the files attached to this post.
Re: RTF control restrictions
Are you sure you included the correct files in that zip? I see a PDF + QRP files, but they're not linked, so there is no test case.. Maybe the zip is missing the RTF file that would be used to statically be displayed in the QRP by your oRTC control? If RB Preview mode truncated the RTF text, then that's a test case.
Re: RTF control restrictions
It seems that there is a maximum length for RTF controls and it seems that it is different between the RTF control and a RTF field in the report builder.
I've tried to copy a .apt file from our application into the RTF and it is cutted after about 1500 lines and then it is not possible to add characters into the RTF.
The report builder prints about 13-14 pages of an RTF and then it ends printing the RTF.
Is there any chance to change this behaviour? The property "Maximum Data Length" doesn't have any effect nor changing the data type from "String" to "Long String".
Nils
I've tried to copy a .apt file from our application into the RTF and it is cutted after about 1500 lines and then it is not possible to add characters into the RTF.
The report builder prints about 13-14 pages of an RTF and then it ends printing the RTF.
Is there any chance to change this behaviour? The property "Maximum Data Length" doesn't have any effect nor changing the data type from "String" to "Long String".
Nils
Re: RTF control restrictions
Did you then copy/paste that into Word or Notepat++, for example, to find out how many characters that was? My guess is that there is a 32K limit, like for multiline fields, for the RTF. (32000 / 1500 = ~21 chars. per line, which is a reasonable average for your apt file.)I've tried to copy a .apt file from our application into the RTF and it is cutt after about 1500 lines...
Well, there is always a chance, but it would be an enhancement request.Is there any chance to change this behaviour?
Well, Long String vs. String wouldn't have anything to do with it, except in the case of the RTF value being fetched from a DB LONG-type column. (See another thread here about the long-running issue of "String" vs. "Long String" for details on what LS is and how/when it's used.)nor changing the data type from "String" to "Long String".
Who is online
Users browsing this forum: No registered users and 1 guest