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

  • Continued Report Problems in 8099

    Web App Running 8099.

    I continue having terrible report issues. When my app was on 7295 all of my reports were fine. Then when I moved to 8000 text was getting clipped. Now I'm on 8099 and text isn't formatting correctly. This is terribly frustrating. Further more, what is rendered in the print preview of Alpha's report maker is NOT what renders in the app (screenshots below). I am wasting so much time trying to fix reports that worked 100% before I updated to 8000 & 8099. It appears the methodology used to render a preview in Alpha IDE isn't the same as it is in the app server.

    This is what renders in Alpha's report maker print preview. Parts of the report are blurred on purpose. This represents what I expect to render in my app.
    Ashampoo_Snap_Wednesday, March 30, 2022_14h36m20s.png



    This is what actually appears in the app. Some commas are out of place. Serval objects missing entirely from the bottom. Overall spacing is off.
    Ashampoo_Snap_Wednesday, March 30, 2022_14h42m3s.png

    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant

  • #2
    I can confirm this behavior. I upgraded my development machine from 7902 to 8099 on 3/26/22. After some testing, I upgraded the WAS yesterday, 3/30/22. I have not modified or published any components.

    I have only tested a few reports, but most of them fail to render the last third of the last page.

    This does not happen on the development machine. Only on the WAS.

    I will save some sample reports before rolling my WAS back to 7902.

    This is a serious problem. Not sure how to build a test case, as I cannot reproduce it on the development WAS.

    Comment


    • #3
      Here is a twist. I use Always Up to run the WAS.

      If I run the WAS without Always UP, no report problems.

      If I run it with Always UP, the report problems occur.

      Comment


      • #4
        For me some of the problems were "fixed" if I removed the RTF controls on my report. My RTF's in the report footer wouldn't show. I replaced them with regular text and it's there now.
        Mike Brown - Contact Me
        Programmatic Technologies, LLC
        Programmatic-Technologies.com
        Independent Developer & Consultant

        Comment


        • #5
          Do you use Always up?

          Comment


          • #6
            Yes, but I can't imagine how that could cause a problem. I'm not in a position to experiment either. Production must move forward.
            Mike Brown - Contact Me
            Programmatic Technologies, LLC
            Programmatic-Technologies.com
            Independent Developer & Consultant

            Comment


            • #7
              Well, if you can find a way to test by launching the WAS without AW, that would confirm that it can be reproduced.

              I will send a bug report.

              Comment


              • #8
                I sent a bug report. Because running the WAS with Always Up is the way to reproduce this, Selwyn's response was not helpful. He said there have been some changes in the way reports are rendered in build 8111, and that there has been no change in AA that would affect AlwaysUp.

                So Alpha is not acknowledging or investigating this as a bug at this point.

                Is there anyone else experiencing this?

                Comment


                • #9
                  Are there no longer any release notes on the nightly builds? It seems the link in Alpha does not have any useful information.
                  https://download.alphasoftware.com/R...easeNotes.Html

                  Comment


                  • #10
                    I helped Cian Chambliss with the initial bug when I first noticed the clipping back in November last year, I am on 8093 and reluctant to upgrade as it works for me and have seen the problems may have returned in later builds. I run alwaysup on my server and it took a few hours for the clipping to manifest itself.

                    If I get time later I will do a temp install of the latest nightly build and see if I get any problems

                    PS I love Pizza as well

                    Comment


                    • #11
                      I just installed nightly build 8011 on my production server. No change, the problem is still there with Always Up. Disappears with no Always Up.

                      I have rolled back to 7902 because of this problem, and also because some submit actions in UXs are not working for me.

                      Comment


                      • #12
                        Originally posted by Pizzadude View Post
                        I sent a bug report. Because running the WAS with Always Up is the way to reproduce this, Selwyn's response was not helpful. He said there have been some changes in the way reports are rendered in build 8111, and that there has been no change in AA that would affect AlwaysUp.

                        So Alpha is not acknowledging or investigating this as a bug at this point.

                        Is there anyone else experiencing this?
                        I've experienced the same behavior on a desktop app.

                        2022-04-01_07-52-25.jpg

                        I was told that it is because A/A no longer uses the ANYUNI printer driver. I was also told to get around this, change to a different font or use html objects instead of rich text objects on reports/letters.

                        I demonstrated that switching to html objects doesn't fix it either and never heard back.

                        Changing fonts is not an option as we have 100's of state approved forms that have to match exactly.

                        Attached Files

                        Comment


                        • #13
                          Tim, are you using Always UP? Does it change if you run without Always Up?

                          Comment


                          • #14
                            Originally posted by Pizzadude View Post
                            Tim, are you using Always UP? Does it change if you run without Always Up?
                            My issue is with a desktop app which does not use Always Up.

                            Comment


                            • #15
                              We had a client point this out to us and I am not sure, but perhaps it has something to do with this:

                              https://aadocuments.s3.amazonaws.com/ReleaseNotes/releaseNotes_2020_to_present.html

                              Classic Server - Report Server - The Report Server was turned off in build 8000. While the Report Server is not needed or used when running under IIS (and Alpha Cloud), it does provide a significant performance benefit when using the Classic Server.
                              Alpha Anywhere V4.6.4.0 - 8000-5628 31 DEC-2021

                              Change in Behavior


                              Report Server - Classic Server - The Report Server is no longer used when printing reports using the Classic Server. This is because now that the Amyuni PDF printer driver is no longer used when printing PDF reports, there is no longer any need for the Report Server.

                              Comment

                              Working...
                              X