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

Return to Previous URL (two screens ago)

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

    Return to Previous URL (two screens ago)

    Hi,

    I have seen on a past post (from Steve Wood) that you are able to go back to a previous page using the following;

    Code:
    It will work if you put this in your initialize event:
    
    if eval_valid("request.referer")
    session.page = request.referer
    else
    session.page = "anerrorpage.a5w"
    end if 
    
    and this in your aftervalidate:
    
    CurrentForm.RedirectTarget= session.page
    
    You only need the else..errorpage.a5w part if you want, probably not necessary under normal circumstances.
    However, what i am trying to achieve is slightly different.

    1. The user selects the search Grid (Page 1) and say lists all companies beginning with A
    2. Then the user selects one of the companies, this sends them to a contacts page (Page 2)
    3. The user then selects the contact and a dialog appears (Page 3).
    4. The user adds some data within the dialog form and then submits the page.
    5. I now want to return to the first grid result page (Page 1).

    I can redirect back to that page, but i will loose the filter results. I want to be able to get back to page 1 complete with the results from the initial filter. I suppose it would be like clicking BACK twice.

    Can anyone help?

    Thanks

    Denis

    #2
    Re: Return to Previous URL (two screens ago)

    I managed to sort it.

    I created another a5w page with some javascript code and redirected my dialog to that.

    Code:
    <script language="JavaScript" type="text/javascript">
    javascript:window.history.go(-3);
    </script>
    Denis

    Comment


      #3
      Re: Return to Previous URL (two screens ago)

      Hi,

      Due to some additional screen clicks in between Page 1 and 3, the javascript go back 3 screens is not always appropriate. Does anyone know a way where i could specifically specify the page to return back to.

      Denis

      Comment


        #4
        Re: Return to Previous URL (two screens ago)

        On the page you want them to go back to, set:

        session.pageiwant=Request.Script_Name

        script_name is the name of the page they are on, like "index.a5w".

        Then use that session variable in a link or response.redirect() on the page you want them to bounce back from. To recreate the initial filter you can either, depending on how you filtered in the first place:

        - on the original page, save the filter text to another session variable and then reapply as a page variable when they go back. (Not sure how you would do the first page, depends on how you set the filter).
        - take a look at the URL on the original page. IF that URL includes the filter syntax, then user request_uri instead of script_name and it will include the filter syntax.
        Steve Wood
        See my profile on IADN

        Comment


          #5
          Re: Return to Previous URL (two screens ago)

          Thanks for the reply Steve,

          Where on the return (original) screen should I place session.pageiwant = Request.Script_Name.

          Denis

          Comment


            #6
            Re: Return to Previous URL (two screens ago)

            Anywhere. Inserting it at the top is best.
            Steve Wood
            See my profile on IADN

            Comment


              #7
              Re: Return to Previous URL (two screens ago)

              Hi all ,

              The page that I'm supposed to add "session.pageiwant = Request.Script_Name" at the top is a page with "requires login" security, so I apparently the code, "session.pageiwant = Request.Script_Name" didn't get transacted before I was directed to my login page.

              SecurePage.a5w
              1. Add "session.pageiwant = Request.Script_Name" at the top

              LoginPage.a5w
              1. After successful login, redirect as session.pageiwant

              Anywhere else I can get "session.pageiwant = Request.Script_Name" transacted before I'm directed to my login page ?

              Thanks.

              Comment


                #8
                Re: Return to Previous URL (two screens ago)

                Jim,

                This is a six year old thread. I am sure the desired method has changed -- please start a new discussion and tell us what you are trying to accomplish.
                Steve Wood
                See my profile on IADN

                Comment


                  #9
                  Re: Return to Previous URL (two screens ago)

                  Hi Steve,

                  ok, here's the new thread.

                  http://msgboard.alphasoftware.com/al...146#post678146

                  Thanks.

                  Comment

                  Working...
                  X