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

Session Expiration

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

    Session Expiration

    How can you detect when a session has expired so when the user clicks on submit I can take them to a page informing them that the session has expired and then they would have to go back to the dialog.

    #2
    Re: Session Expiration

    I don't know how to detect when Alpha's session expires, but you can find javascript that counts the seconds of inactivity, and then pops an alert dialog box when a time threashold was met. So, if your WAS is set to one hour, you set the javascript to 55 minutes to pop an Alert saying the session is about to expire unless you refresh the page. Or the timer could be set equal to the WAS and say "You've timed out" and then on OK, redirect to a new page. I have some of this somewhere if you can't find it.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Session Expiration

      Steve, I found a temporary solution without using a javascript within the dialog

      Code:
      [B][COLOR="blue"]Component Initialize[/COLOR][/B]
      session.FlagIsLoggedIn = .t.
      
      [B][COLOR="Blue"]Component Validate[/COLOR][/B]
      
      if eval_valid("session.FlagIsLoggedIn") = .f. then
          response.redirect("timeoutwarning.a5w")
          end
      end if
      The downside is that they will not know that the session has expired until they hit submit....I will try to refine but this will work for now. The timeoutwarning page is simply a message about the session expiring and a button to click to return to the dialog.

      Thanks

      Comment


        #4
        Re: Session Expiration

        Phil,

        Has this work well for you and/or have you improved it any?

        I am having some problems with people being logged in for too long at a time, losing their session variables and then complaining that something is wrong with the database. I tell them to log out and then log back in - in most cases that is the only problem.

        This looks like a decent solution so I wanted to check with you before I implement it to see if you have made any improvements. Thanks!

        Mike

        Comment


          #5
          Re: Session Expiration

          I thought that this was one of the uses of eval_valid, i.e., if you always use eval_valid wheneber you use a session variable than you can redirect the user to any page you want when that session variable no longer is "valid", i.e, the session has expired.

          So

          if eval_valid("session.anything")
          .
          .
          .
          else
          response.redirect("go to apge that says "Your session has expired, and offeres the login compoent

          end if


          Gary
          Gary S. Traub, Ph.D.

          Comment


            #6
            Re: Session Expiration

            I am sorry but I thought I had answered this thread on what I had found. The problem actually turned out to be a path problem. Thru out my pages I was using the following format https://www.domain.com In ONE location I had https://domain.com When the user tried to go to the domain.com then the session was terminated. Inserting the www to the path corrected my problem.

            Comment


              #7
              Re: Session Expiration

              Great point Gary, I can see where that would work. I guess I can actually place that on any page that is entered into as well as in the event CanUpdateRecord. I will give that try. Thanks!

              Comment


                #8
                Re: Session Expiration

                Phil - I looked and sure enough, I too have a couple of site references without the www!

                I am going to search the rest of my database for similar problems and I am going to use the "eval_valid("session.variable") to make it even a bit more bullet proof.

                Thank you for your help Phil and Gary!

                Comment


                  #9
                  Re: Session Expiration

                  Originally posted by Steve Wood View Post
                  I don't know how to detect when Alpha's session expires, but you can find javascript that counts the seconds of inactivity, and then pops an alert dialog box when a time threashold was met. So, if your WAS is set to one hour, you set the javascript to 55 minutes to pop an Alert saying the session is about to expire unless you refresh the page. Or the timer could be set equal to the WAS and say "You've timed out" and then on OK, redirect to a new page. I have some of this somewhere if you can't find it.
                  I was looking for something similar to use in my Home Page containing Tabbed UI, if you can please share it here Steve!

                  Thanks in Advance!

                  Comment

                  Working...
                  X