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

Problem with remote user timing out on uploads

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: Problem with remote user timing out on uploads

    The different agency is logging on to our application server thru the web browser. I don't know what web browser they are using or what network/browser controls they have. One of our people is going up to Bellingham (where they are located) to work with the user and their IT people to see if the problem can be solved. We have not had complaints about time outs from our other users since I moved the validation logic from Alpha to a SQLServer stored procedure on Saturday.

    Comment

      #17
      Re: Problem with remote user timing out on uploads

      This is my only web/Alpha application. What is best practice for running long processes? Is there a way to run them in a background process?

      Comment

        #18
        Re: Problem with remote user timing out on uploads

        Yes, but it depends on the process. I don't think, for instance, that you could move an upload process to the background because it relies on getting the document from the user's computer. After the file is fully uploaded, you could probably process the file in a background process though.

        What are you trying to offload?

        Have you used Alpha Desktop at all?

        Comment

          #19
          Re: Problem with remote user timing out on uploads

          I have not used Alpha Desktop. All my desktop/client-server applications are in PowerBuilder. We only introduced Alpha because we needed a Web application that had to be translated out of Oracle HTML because we were getting rid of Oracle and moving to SQLServer.

          This question was initially because we have users uploading data into a central database. The validation processing after the upload is extensive. At this point, I have moved all of the validation processing to a SQLServer stored procedure, but since the call to the stored procedure is at the end of the file load, it still ties up the user's computer. I also thought of what would be happening if the user were running a very large query or report.

          30 years of programming experience, but this is my first and only Web project. Different way of looking at things.

          Comment

            #20
            Re: Problem with remote user timing out on uploads

            Does the user need to work on the uploaded data immediately after the upload or can they wait? Because normally a background process would run at intervals. So depending on when the upload completed you would have to wait not only for the processing to complete, but also until the next processing cycle as well as maybe wait behind other uploads that happened before yours.

            Also, do you need to notify the user when the processing is completed or are they hands-off after the upload?

            And yes, web projects are very different from desktop projects.

            Comment

              #21
              Re: Problem with remote user timing out on uploads

              The user can wait to work on the uploaded data. The user would prefer to be notified once the upload is complete, before the validation processing, but the only way I have figured out how to do that included the user having to 'click ANOTHER button' which they did not want. So now they have a file upload that puts the data into a pre-processing table and immediately calls the stored procedure to do the validation processing. By moving the validation to a stored procedure, I reduced the time from 15-20 minutes to ~2 minutes for a 500MB file. This has made the users much happier. It did solve the 'timing out' issue. I read what I could find about using a separate thread to call the stored procedure, but most of it seemed to pertain to 'Desktop only' and when I tried it, it debugged as successful, but did not actually run the stored procedure. I'm not sure why my boss thinks a background thread is a good idea, since the user can't work with the data until the validation processing is complete anyway. I could see the point if it was a long running report, where the user could go do something else within the program while the report was processing. I've also never developed a multi-threaded application.

              Comment

                #22
                Re: Problem with remote user timing out on uploads

                If you want to try out a background process, here is the quick and dirty method:

                Create a UX with an ontimer event of 15 minutes (or whatever is appropriate).

                The event will fire an xbasic procedure (from a JavaScript action) that does the following:

                Check to see if there is any new work to process - if there is, then do the work.

                You can have the xbasic function fire the stored procedure and then send an email when it's done.

                You put that onto an a5w page and you run the a5w page directly on the Alpha server. Just leaving it running 24/7. (Note: You could technically run the a5w page on any machine, it doesn't matter - I do mine from the server.)

                The problem with doing that is that if Alpha ever crashes or if the server reboots, then you have to manually reload the page.

                BUT - this will let you know if this is a path you want to pursue further.

                Comment

                Previous 1 2 template Next
                Working...
                X