We're having quite a few problems with the Telerik reporting tools. Perhaps these issues are all just something we're doing wrong (and frankly we'd be happy if they were), but we're starting to believe that it's really a series of bugs in the product. This one we refer to internally as "Broken Borders".
Broken Borders
Essentially, all we really want to do is put a border around a report; a simple 1 or 2 pixel solid black line. We can do that and get it to render okay in the preview, but when we add data it suddenly will stop rendering the left and right borders correctly and, depending on how the report was rendered, will sometimes put a bottom border in where it doesn't belong.
I have attached screenshots from within Visual Studio. Unfortunately, I can't attach rendered PDFs or rendered TIFFs, but those are in my support ticket along with the source code for the report definition. If this is caused by something we're doing wrong then please tell us what it is because this happens on all of our reports. If, on the other hand, this is a limitation with the Telerik product then please let us know ASAP so that we can begin evaluating other products and start the refund process.
One work-around that was suggested is to determine the maximum number of detail rows the report could render and "pad" our source data to meet that number. Unfortunately, this work-around isn't acceptable given our situation. Using a row count is nearly impossible if word wrapping (TextWrap=True) is enabled in any of the cells and, in our case, it is.
Greg
Broken Borders
Essentially, all we really want to do is put a border around a report; a simple 1 or 2 pixel solid black line. We can do that and get it to render okay in the preview, but when we add data it suddenly will stop rendering the left and right borders correctly and, depending on how the report was rendered, will sometimes put a bottom border in where it doesn't belong.
I have attached screenshots from within Visual Studio. Unfortunately, I can't attach rendered PDFs or rendered TIFFs, but those are in my support ticket along with the source code for the report definition. If this is caused by something we're doing wrong then please tell us what it is because this happens on all of our reports. If, on the other hand, this is a limitation with the Telerik product then please let us know ASAP so that we can begin evaluating other products and start the refund process.
One work-around that was suggested is to determine the maximum number of detail rows the report could render and "pad" our source data to meet that number. Unfortunately, this work-around isn't acceptable given our situation. Using a row count is nearly impossible if word wrapping (TextWrap=True) is enabled in any of the cells and, in our case, it is.
Greg
1 Answer, 1 is accepted
0
Greg
Top achievements
Rank 1
Rank 1
answered on 12 Dec 2012, 02:47 PM
For anyone else struggling with this issue, be advised that support has indicated that it's a known issue that they intend to address in the Q3 service pack. There is no bug or issue number to be tracked, however, and there are no internal builds or anticipated release date.
Good luck,
Greg
Good luck,
Greg