Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Continued Report Problems in 8099

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #61
    It turns out there is another way to print an HTML field on a report, without using an HTML object in the report.

    Create a calculated field such as MyCalculatedField = printHTML(FieldName) where FieldName is the field name retrieved from the database, and contains the text or blob data with the HTML you want to put in the report.

    Now drag the calculated field into the report. Make sure the Name property in the field is CALC->FieldName.

    For my case, there is no longer an issue with spilling text over into an additional page, even though The Growable property for the field on the report is checked (apparently by default).

    AND the pdf.css file works in this situation. The release notes say "Reports - HTML Content - Default Style Sheet - pdf.css - If a PDF report contains an HTML control" but this appears to be inaccurate. pdf.css had no effect in my case when using an HTML control. Only when using printHTML().

    So I am doing away with all my HTML objects on reports and using printHTML().



    Comment


      #62
      Good - well done.
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #63
        There's more...

        I have created 2 reports. They each contain 2 objects. The first is an RTF object with some text. The second is an object populated with a calculated control using printHTML().

        The problem I am seeing is the spacing of the text in the second object.

        If the text in the first object is not long enough to push the second object to the second page, it looks like this:

        GoodReportText.png

        If the text is long enough that it pushes the second object onto the next page:

        BadReportText.png
        The only difference between the two reports is the length of the text in the RTF object.

        This only happens when launching the UX in Live Preview or in a browser and then running the reports. It does not occur when previewing the reports in the Report Editor or when opening the UX in Working Preview.

        Attached is a simple UX that demonstrates this, and the pdfs of each report.

        I'm looking for some folks to test this to see if they get the same result.



        GoodReport.pdf

        BadReport.pdf

        TestPrintHTML.zip

        Comment


          #64
          It turns out the print spacing is a bug. It is fixed in tomorrow's nightly build. Selwyn says there will be a new stable build released soon. Possibly sometime next week.

          Comment


            #65
            That's actually good news.
            I think it would be great if Alpha separated the nightly builds between fixes (Safe to apply to production environments) and pre-releases (Not confirmed safe for production environments).
            Gregg
            https://paiza.io is a great site to test and share sql code

            Comment


              #66
              Originally posted by madtowng View Post
              That's actually good news.
              I think it would be great if Alpha separated the nightly builds between fixes (Safe to apply to production environments) and pre-releases (Not confirmed safe for production environments).
              Absolutely 100% agree that this is how it 'should' be done Gregg
              Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

              Comment


                #67
                Hi All

                Re the "print spacing is a bug" does anyone know when we will see a fix for this, the latest Build 8282- 5653 08 AUG 2022 makes no mention of it.

                I am having a lot of issues with this problem and nothing I do seems to fix it...

                Thanks
                B

                Comment


                  #68
                  Grasping at straws as I don't have any of the issues running your test case and I'm om 8099 - maybe check you printer drivers ..

                  Drivers.png
                  Insanity: doing the same thing over and over again and expecting different results.
                  Albert Einstein, (attributed)
                  US (German-born) physicist (1879 - 1955)

                  Comment


                    #69
                    so far so good with all of my reports since moving to the latest stable build. I do notice that if I double space a line item, like start a new paragraph it pushes all of my line items to the next page and really messes with the spacing but I think it's probably not really a bug as I made several different layout pdf reports using the same info and only a couple of them render the spacing wonky - the rest are fine so the problem is most likely bad choices in designing the layout...
                    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                    Comment


                      #70
                      Originally posted by Pizzadude View Post
                      It turns out the print spacing is a bug. It is fixed in tomorrow's nightly build. Selwyn says there will be a new stable build released soon. Possibly sometime next week.
                      Looks like they missed the mark a little. Wonder if they decided to wait until DevCon for the new release.

                      Comment


                        #71
                        New stable build!

                        Alpha Anywhere V4.6.4.3 - 8301-5654 26 AUG-2022

                        Reports - HTML - PDF - Fixed some issues where reports that contained HTML content did not render correctly when output as PDF.​

                        It looks like the text spacing problem described in post Alpha Five v4 is fixed.

                        Time for some testing!

                        Comment


                          #72
                          After testing for known issues and finding none, I deployed 8301 to my production server.

                          I found that Context.Security.CallResult is failing. So I rolled back to 7902.

                          Never had this problem in any previous build.

                          I believe I will start a new thread for this.

                          Comment

                          Working...
                          X