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
Devcon 2020 Goes Virtual! LEARN MORE >

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

App Server Update Causes Printing Problem

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    App Server Update Causes Printing Problem

    Hopefully, someone can help with this.

    On Thursday, I updated to the newest build of Alpha (Developer and Application Server).

    I received a call, on Friday, from a user, that a PDF report that he has been running daily, for several months, without issues (action button on a Grid that uses "Grid Filter" and "Grid Order") will no longer run. It just pauses forever at the "Working" message.

    I tried it and had the same problem. The PDF report doesn't create (just stays on the "Working" screen).

    I have looked at the code and it's a pretty simple report (which compiles/formats instantly from Alpha's Developer version). This is definitely a problem with the Report Server on the latest Application Server build that I uploaded.

    In desperation, because my customer needs the report at 6am, I've reinstalled the previous version of the Application Server Patch (from ~5/27). The report now compiles in less than 20 seconds (still longer than I'd like... but reasonable and acceptable).

    Has anyone else had an issue with the latest Application Server build, with regards to PDF Report printing? Is there something I need to change in the Application Server, so that I can install the latest version and still run reports.

    I'd appreciate any help.

    Thanks,
    Phil
    Tags: None
    #2
    Re: App Server Update Causes Printing Problem

    I have not experienced any issues with PDF with the latest official build.
    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

    Comment

      #3
      Re: App Server Update Causes Printing Problem

      I'm on build 3678_4685 and my reports seem to be working okay. I know there have been some code changes recently to implement html-paged reports so it's very possible something in the change is affecting your particular application.
      If I were you, I'd send a bug report, though it's sometimes hard for them to track down unless they can reproduce the problem.
      Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

      Comment

        #4
        Re: App Server Update Causes Printing Problem

        On Thursday, I updated to the newest build of Alpha (Developer and Application Server)....

        So you're on a pre-release? ...send a test cast to Alpha and they will fix it.
        Mike Brown - Contact Me
        Programmatic Technologies, LLC
        Programmatic-Technologies.com
        Independent Developer & Consultant​​

        Comment

          #5
          Re: App Server Update Causes Printing Problem

          Hi-

          Thank you so much for writing back. That's excellent information. I WAS on 3670-4684. Of course, now that I loaded the older build (3629-4676, which is working), I'm obviously not on the latest build. With this "older" build, my customer was able to run his reports this morning and this afternoon, without issue.

          NOTE: Not that it matters, I didn't go back to an earlier version of the Developer program, I'm still on 3670_4684.

          Since neither of you had any issues with your PDF reports, tonight, I will try to re-apply the 3670_4684 (or even Friday's Pre-Release build: 3678-4685) Application Server Patch to see if there are any issues. Maybe it was just an issue with the "patch" I applied (of course, I'll re-download a new copy tonight).

          Do you think there's any value in downloading/installing the "full file" vs the "patch", in this case?

          Anyway, thanks for your help. I will update this post with the results of tonight's update

          Comment

            #6
            Re: App Server Update Causes Printing Problem

            Originally posted by psamuels56 View Post
            NOTE: Not that it matters, I didn't go back to an earlier version of the Developer program, I'm still on 3670_4684.
            Best practice is to always keep the Developer and Server at the same build revisions.

            Originally posted by psamuels56 View Post
            Do you think there's any value in downloading/installing the "full file" vs the "patch", in this case?
            I wouldn't, that shouldn't be necessary.
            Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment

              #7
              Re: App Server Update Causes Printing Problem

              Thanks, Stephen. I ALWAYS keep the editions in sync. The ONLY reason they aren't in sync now is that I had to downgrade the Application Server to get the print function to work (there was no point in downgrading the Developer program at this point). Once the issue is resolved, I'll make sure that the two builds are in sync

              Comment

                #8
                Re: App Server Update Causes Printing Problem

                I'm having issues with 3670_4684 and PDF reports as well (whether freeform or layout table). I converted one of my Free Form reports to layout table report and I got it to print (though it still seems slower than it use too) but then when I try to get a PDF of that file it only works with smaller reports (4-5 pages), larger reports never download the PDF. I need the PDF as I put signature fields on the report and they don't seem to show up when I use the "Print HTML" button (also my page breaks don't work properly using the "Print HTML" button). I originally was using the XPS print driver (with the box checked to automatically convert to PDF) but wasn't able to get the reports to print (even in HTML) until I switched this off.

                I haven't yet tried to roll back to a previous version yet as I was hoping there might be some more information from others on this issue, anyone?

                Comment

                  #9
                  Re: App Server Update Causes Printing Problem

                  It seems my report issues may have been related to having a linked report. After I rebuilt the query so it would work with a single report and then restructured the main report to handle all the breaks (rather than linking a report) it is now allowing me to run my reports as PDFs. I did also roll back to version 3633-4676 (but before I did the reworking of the report the PDFs still had issues). The main reports query only took about 2.5 seconds to run in mysql and the linked report only took 3/4 of a second so I don't think the query was overly complex (those times are for running the report when it would have roughly 45-50 pages due to the group breaks). Just wanted to give an update, look forward to rolling it back to the newest version this weekend and seeing if the report still works (I'll try to remember to post back here what I find).

                  Comment

                  Previous template Next
                  Working...
                  X