Text getting cut off

Originally Posted 9 September 2009, 1:05 am EST

  • Originally Posted 9 September 2009, 1:05 am EST

    Hi,

    I am using VS 2008 and Active Reports 6.0.



    Whenever I generate a LONG active report the text of last line of one page appears in the first line of next page. Also some text gets cut off.



    Please let me know the solution ASAP.



    Thanks,

    Srinivasan.T
  • Reply

    Can you send us the rdf?  Is this long text getting assigned through code or is it coming from a db?
  • Reply

    Ankit,

    Herewith I have attached a JPG file which explains my problem. Some text got cut in that report which I'll explain over phone on Monday. Also if you notice the last line of the text appears in the first line of the next page too.



    Actually I need to generate two type of reports one with "keepTogether" set to "false". Another one with "KeepTogether" set to "true".



    I am facing problem when I set "keepTogether" set to "false".
    2009/09/Report_text_cutoff.JPG
  • Reply

    I sent you an email.
  • Reply

    Hi,

    I have sent both RPX as well as RDF files through email. Please have a look at it.



    Data is coming from the database.



    Thanks,

    Srinivasan.T
  • Reply

    Hello Srinivasan,

    Is there any specific reason that you cannot set KeepTogether property to true? I would request you to please provide us the RDF file of the report in which text is getting cut off. You can find information on saving and loading of RDF files over here.

    Regards,
    Ankit Nigam

  • Reply

    Rpx file is attached
    2009/09/rptSignoutVert.rpx
  • Reply

    How much of text does the second record contain?  It might be that second record is not able to render in space available so it moves to the third page.

    we need to see the rdf as Ankit mentioned in order to investigate the
    text cut off issue.  If you can provide the report itself, that would
    be helpful too.  A small project that will demonstrate this issue to us will be very helpful.



  • Reply

    .vb is attached
  • Reply

    Ankit,

    If I set the KeepTogether property to True then I am getting the foll. issue.



    Suppose there are five records. The size of the first record is 1.5 pages (i.e) First record occupies first page and half of page two. Then the second record starts in the third page only and NOT IN second page itself.





    But I need the second record to start in the second page itself.



    Please provide me some solution to overcome this issue. Is this bug is in the Active Reports software itself? If so please let me know. Because many users are facing the same issue which I can see in the internet and I didn't get any solution.



    Thanks,

    Srinivasan.T
  • Reply

    Ankith and Raj,

    Herewith I am attaching the original files that I am using in the project. Please let me know if you need anything else from my side.



    Thanks,

    Srinivasan.T
  • Reply

    vb file is attached
  • Reply

    srinitj1,

    Thank you for the details. I would request you to allow me some more before I can provide you a solution for this issue.
    Thank you for your patience thus far.

    Regards,
    Ankit Nigam
  • Reply

    Ankith,

    Herewith I have attached the RDF file. Shall I wait for your reply? Shall I know how much time it'll take? If its going to take too much of time I'll leave now.



    Also If you see the last line of page 3 its getting repeated in the first line of page 4.



    Also some text has got cut off in the page 4.(i.e) Past Medical history 20 should be there.


    2009/09/SignoutReport.rdf
  • Reply

    Ankith,

    Please call me.



    Thanks,

    Srinivasan.T
  • Reply

    Ankith,

    I have sent the rpx and resx files to support@grapecity.us.com. Please have a look at it. I am not able to send the .vb file.



    Please call me on 9845784585 right now if possible.



    Thanks,

    Srinivasan.T
  • Reply

    Ankith,

    Datadynamics website is not allowing me to attach the vb file. Please give me your email id so that I'll attach the files and send it.
  • Reply

    Ankith,

    Did you get any solution for the issue?



    Thanks,

    Srinivasan.T
  • Reply

    Hello Srinivasan,

    I would like to inform you that the case 135851 is at the high priority at the moment; however currently I cannot provide any particular ETA for this case. I have already attached your E-mail address to the list of affected users for this case. You will be notified once a fix for this case is available.

    Do let me know if you require further assistance/clarification.

    Regards,
    Ankit Nigam

  • Reply

    Ankith,

    Is there any progress?



    Please let me know.



    Thanks,

    Srinivasan.T
  • Reply

    Hello Srinivasan,

    I am able to reproduce the issue at our end. I have opened a new Case 135851 to get this issue addressed. I have added your E-mail address as an affected user to this case. You will be notified once a fix for this case is available. Do let me know if you require further assistance/clarification.

    Regards,
    Ankit Nigam

  • Reply

    Ankith,


                     Please let me know if there is any progress.


    Thanks,


    Srinivasan.T

  • Reply

    Hi ,

    Did you get any solution
  • Reply

    fandc,

    Unfortunately the implementation of Case 135851 has been postponed since it requires many major changes in the ActiveReports engine. If you are facing similar issues, then could you please provide me a small sample application which replicates this issue so that I can take a look at it and try to find any workaround.

    Regards,
    Sankalp
  • Reply

    Has this Case 135851 been addressed in any version (6, 7, or 8) of Active Reports?
  • Reply

    miknue,

    Unfortunately Case 135851 is still open. We have asked the concerned team to provide their thoughts on this and we will update you as soon as there would be any information available.

    Apologies for the inconvenience caused.

    Regards,
    Sankalp
  • Reply

    Could you provide an answer if this issue affects ActiveReports version 7 and 8 as well?
    As we are using a workaround currently with our existing system on ActiveReports 6 and have moved to ActiveReport 7 with our newer versions.

    Thanks!

    Regards,
    Yeo
  • Reply

    Hi,
    We are having the same problem in AR6 and now migrated to AR9.

    Has it been finally fixed in AR9 or AR10?

    Thank you,
    Krupek
  • Reply

    Yeo,

    This issue only occurs under certain conditions and generally will never be observed during report creation. Since Case 135851 is open with the development team, this issue may affect ActiveReports 7 and 8.

    Regards,
    Sankalp
  • Reply

    If the answer is NO, then are you going to fix it EVER?
    If still the answer is NO, then we need to know some usable and stable workaround how to print long texts which ARE NOT cut off.

    Regards,
    Krupek
  • Reply

    Hi,

    I cannot force any fixed layout of the report as they are created by the clients of our software.
    Moreover we proved many times that changing the layout fix only the current scenario (for the particular data) but the problem will reoccur after some time for a different scenario (with the new data).

    We need to know either of the two:

    1. What are the conditions when the issue can occur. If we know the conditions we can try to prevent this issue by using templates which do not meet them. In other words give us some universal guideline HOW to avoid it.

    2. How to write a code which can detect when this issue occured for the generated report (RDF). Having such "a tool" we would be able to warn the client that the report need to be recreated because it contains "cut text between the pages".

    I am also attaching a few examples of the problem (I spent an hour just playing with the designer and found it).
    2016/01/Modified_testCase1.rpx

    2016/01/Modified_testCase2.rpx

    2016/01/Modified_testCase3.rpx

    2016/01/Modified_testCase4.rpx
  • Reply

    Hi Krupek,

    Unfortunately, it is not possible for the development team to fix this issue due to the risks and the complexity involved. We would require many changes throughout the engine and hence, is risky for the other modules of the product.

    We would suggest you to start rendering the report from a small margin at the top. For the report provided(see attached) by some other customer, each of the following approaches works:
    1. Set the Top Margin of the report to 0.06 in.
    2. Set the Height of the PageHeader section of the report to 0.06 in.
    3. Set the Y Location of the Textbox in the detail section to 0.06 in.

    Please note : You need to modify your report file, as per the suggested workaround, accordingly.
    Let us know if you face any problem in implementing the same.
    We apologies for the inconvenience faced.

    Regards
    2016/01/Modified_testCase.zip
  • Reply

    Hi,

    Thanks for your investigation on this issue.
    This problem generally appears when TextBox control crosses multiple pages, along with having Zero(or very less) page margins. However, the occurrance of this issue fully depends on layout of the report(size & position of controls) and Page Settings(Margins etc).

    To avoid cutting of text in such scenarios, you are suggested to set the page margins to some considerable value. You might need to do calibration of values while setting Margins, TextBox position, size etc.
    Unfortunately, it is not possible to detect occurrence of such issues using some tool/custom code etc.

    To avoid cutting of Text, we have made following changes in the reports provided by you:
    Modified_testCase1.rpx -- Set Top margin to '0.06 in' instead of '0.00 in'
    Modified_testCase2.rpx -- Set Top margin to '0.06 in' instead of '0.00 in'
    Modified_testCase3.rpx -- Set Top margin to '0.06 in' instead of '0.00 in'
    Modified_testCase4.rpx -- Set Top margin to '0.06 in' instead of '0.00 in'
    Modified_testCase5.rpx -- Set Top margin to '0.25 in' instead of '0.00 in'
    Modified_testCase6.rpx -- Set Top margin to '2.00 in' instead of '0.50 in'
    Modified_testCase7.rpx -- No change in Margin, remove overlapping of TextBoxes(TextBox1.Y = 9.33 in)
    Modified_testCase8.rpx -- Set Top margin to '0.80 in' instead of '0.60 in', set 'WrapMode' property of TextBox2 to 'WordWrap'.

    You can note that, by making minor changes in the layout of report, cutting of text can be avoided. Modified reports are attached.
    Thanks & Regards
    2016/01/Modified-Reports.zip
  • Reply

    Hi Krupek,

    We understand your situation and apologize for the inconvenience.
    We have forwarded this issue to the concerned team(Tracking ID: 135851) for further investigation. We will get back to you as soon as we get any update from them.

    .
    Regards.
  • Reply

    Shubham Srivastava,

    This is NOT the solution at all!

    Our clients does not have static reports. Each and every report differs. This is why we chosen Active Reports - to generate various reports dynamicly using a single layout!

    Our clients have a field which is used to print long text, and the text can be anything... from a single line to a multiline/multiparagraph long text, from a smaller font to the bigger font, with and without formatting etc. And this field can be printed anyware on the page as there are other dynamic fields above this particular field.

    We cannot modify layout of report for each and every report independently. And what is worst is that we don't know which reports to correct as there is no way to catch that the problem occured.

    [u]Please escalete this issue to the senior management.[/u] We need to have either solution or workaround or at least tool to find affected reports.

    Krupek
  • Reply

    Any update?
  • Reply

    Hi Krupek,

    The issue is still under investigation at our development team’s end.
    We will get back to you as soon as we get any update from them.
    Apologies for the delay.

    Thanks
  • Reply

    Shubham,
    Any update?

    Krupek
  • Reply

    Hi Krupek,

    The development team is still investigating this issue. We apologize for the delay.
    We will get back to you as soon as we get any update from them.

    Thanks
  • Reply

    Shubham,
    Has this been addressed?

    Krupek
  • Reply

    Hi Krupek,

    The issue is still under investigation at our development team's end.
    We will get back to you as soon as we get any update from them.
    We appreciate your patience.

    Thanks
  • Reply

    Hello Krupek ,

    unfortunately, after developer's research, PMs decided to not fix this issue (Case 135851).

    Thanks,
    Sergey Romanov.
  • Reply

    Hi,

    Has this been finally fixed? In what version?

    Are mentioned Modified_testCase1.rpx ... Modified_testCase10.rpx work correctly now in the newest AR release?

    Thank you.
  • Reply

    Shubham,

    Has this issue been escaleted to the senior management? Active Reports does not work for the very simple examples I provided above! We need a fix or at leaset a code/tool to find all affected reports to warn our clients that the report needs to be regenerated.

    Thank you,
    Krupek
  • Reply

    Shubham, Sergey,

    It's more than a month since the last update...

    Is the issue fixed?
    Is the a code/tool to find all affected reports ready?

    Thank you,
    Krupek
  • Reply

    Hello Krupek ,

    we already got the results of research from the developers team.
    unfortunately, fix can break the existing reports and estimate does not allow to implement it asap.
    i have forwarded your request about code/tool to developers.

    Thanks,
    Sergey Romanov.
  • Reply

    Hello Krupek ,

    at present, this issue is assigned to ActiveReports 10 SP2 (~Jule 2016).
    developers were not able to create the requested tool yet.

    Thanks,
    Sergey Romanov.
  • Reply

    Sergey,

    What does it mean "decided to not fix"? This is a confirmed bug (that is present on multiple versions for a couple of years) but you are NEVER going to fix it?

    Thank you.
  • Marked as Answer

    Reply

    Hello Krupek ,

    yes, it is correct, issue won't be fixed. now this issue is treated as a limitation in the product functionality.

    Thanks,
    Sergey Romanov.
  • Reply

    Hello,
    could you please advise if this problem is fixed in some present version of Active Reports or do you have any estimate as to when?
    Thank you.
  • Reply

    While  this thread is really old, we experienced this problem recently when replacing the contents of null or blank fields with long placeholder values. After following all of the advice regarding textbox height etc, the issue remained. Changing the height of the offending field(s) to a larger value on the detail_beforeprint event got around the issue. The same principle was applied elsewhere in other report sections where the problem existed. We're still using active reports 6. 
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels