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

Successful 6 Instances of WAS

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #76
    Re: Successful 6 Instances of WAS

    Perhaps other solutions are to not use any of the functions that call the print driver, build pure html reports from scratch or use an SQL-based report writer and call the report. I think I've avoided this problem on my 18-instance web app because I don't use the report.saveas() function anywhere, the reports are all hand-coded exports and rendered html pages. That was just how the application was designed, I wasn't aware of any print driver issue at the time.
    Steve Wood
    See my profile on IADN

    Comment


      #77
      Re: Successful 6 Instances of WAS

      Great idea Steve. Maybe I will need to go that route later.

      I'm with you I didn't know of any problem either until I had multiple crashes.

      From my understanding Amyuni does have a driver that will handle the queue but it is not the one included with the WAS License.

      That would be a feature pack that I would buy right now.
      Chad Brown

      Comment


        #78
        Re: Successful 6 Instances of WAS

        Would there have been any way to direct all print jobs to the same instance?

        Comment


          #79
          Re: Successful 6 Instances of WAS

          Originally posted by chadbrown View Post
          Great idea Steve. Maybe I will need to go that route later.

          I'm with you I didn't know of any problem either until I had multiple crashes.

          From my understanding Amyuni does have a driver that will handle the queue but it is not the one included with the WAS License.

          That would be a feature pack that I would buy right now.
          I agree with Chad that Amyuni driver with queue is the best option.
          Other options are using beside the solution from Steve external report writers like Jaspers, Microsoft Report Service but most A5 folks use Alpha Software Report Writer.

          Comment


            #80
            Re: Successful 6 Instances of WAS

            So is the queued Amyuni driver just something purchased and installed separately? If so, why didn't you go this route Chad?

            I find this all really disappointing because Alpha specifically touted the ability for multiple users to call the same report at the same time in one of the pre-10.5 v10 upgrades.

            Comment


              #81
              Re: Successful 6 Instances of WAS

              Supposedly you cant the original one is integrated into the was. If it was a way to go trust me I would have.
              Chad Brown

              Comment


                #82
                Re: Successful 6 Instances of WAS

                Stupid Idea:

                why not duplicate the reports for each server eg.
                invoice_server1
                invoice_server2
                so that each server can only access their own set of reports using some kind of session variable
                Cheers
                Mauricio

                Comment


                  #83
                  Re: Successful 6 Instances of WAS

                  They all work off the same webroot same pages same grids and its not only when they click on the same report any two reports in combination can trigger the problem.
                  Chad Brown

                  Comment


                    #84
                    Re: Successful 6 Instances of WAS

                    Thats why I said it was a stupid idea :D
                    Cheers
                    Mauricio

                    Comment


                      #85
                      Re: Successful 6 Instances of WAS

                      There are questions on the Amyuni board about "spool" or queue jobs on the vendor website.
                      But that is not the package that is supllied with AlphaSoftware there using the embedded "developer edition" you can check this by the Amyuni printer driver and check preferences. There is no option to change preferences so maybe in the Amyuni "Pro" version you can. No idea or that this package is supported by AlphaSoftware,

                      Also it's unclear that by using the Amyuni PRO version the WAS will keep running you don't have a "hang" on your system or have to reboot at the end of the day as serveral folks reported on this board.

                      A normal situation is that a printer [driver] device supports spooling.
                      I could be wrong in this situation that A5 and Amyuni driver do support the spool option then there are other reasons the WAS hangs, for what I don't have the right answer.

                      Comment


                        #86
                        Re: Successful 6 Instances of WAS

                        Eric I don't think I have ever said it doesn't support spooling. Maybe I am missing your point or its not directed at me. My problem is Amyuni ends up with multiple documents and will not print them out. And for me it does hang the WAS instances, and I can reproduce the problem if I want to. Also Alpha employee has confirmed that it is a problem and that's why they have a work around for the problem that they will gladly build for you at 150/hr. It uses the desktop version to create a queue table and then you can build a grid to access the created pdf files.
                        Chad Brown

                        Comment


                          #87
                          Re: Successful 6 Instances of WAS

                          About a month ago I contacted Amyuni and was told that I could not run their Pro version with Alpha. The way it is designed, if I install the Pro version, it will be overwritten by the Alpha Amyuni version every time I try to print through Alpha.

                          Pat
                          Pat Bremkamp
                          MindKicks Consulting

                          Comment


                            #88
                            Re: Successful 6 Instances of WAS

                            ?? Also Alpha employee has confirmed that it is a problem and that's why they have a work around for the problem that they will gladly build for you at 150/hr. It uses the desktop version to create a queue table and then you can build a grid to access the created pdf files.
                            __________________

                            A desktop workaround ?
                            we talking webapps here, I hope there is an other solution to solve this
                            then to reset the server at the end of the day at large projects you need a bike or stay at the office

                            thanks for sharing

                            Comment


                              #89
                              Re: Successful 6 Instances of WAS

                              Ya exactly my opinion. I do have a temp fix which involves Always up and a sanity check to kill off the printing queue and if that doesn't work then it will restart the machine. Not exactly what we are after due to the user(s)loosing the report(s) that they were looking to print.
                              Chad Brown

                              Comment


                                #90
                                Re: Successful 6 Instances of WAS

                                I can understand that you use a desktop module for batch print large amount of invoices etc as type of background jobs nothing else I can think off, hope it will be solved in the future, knowing the guys at Alphasoftware there will come a solution [as always]

                                Comment

                                Working...
                                X