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

WAS sessions variables

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

    WAS sessions variables

    Peter Wayne asked about using a session variable in a filter. I am trying to do exactly this. However I may not be declaring the variable correctly. I am declaring the variable session.user_name = "eval(user_name)" in a login dialog activate event. I then set the filter user_name = "eval(session.user_name)" in a grid component query (dbf). Zero records are returned. I can't see what I am missing.

    Thanks for any help

    #2
    RE: WAS sessions variables

    John

    I don't think a session variable will evaluate directly in the component. However, you can add code on a WAS page that uses the component to use a session variable. If you look at the xbasic tab when the component is in edit in the component builder, you will see a line like this if you have set a filter in the component

    tmpl.DBF.filter = "Customer_Id=\"\""

    In this case, the filter was to find all records with a blank customer_id using the Alpha Sports Invoice_header table. That should return 0

    Now build a page and insert the component. On the source page, you will see this

    '==============compute the HTML for the Component==========

    delete x_TestInvoice
    dim x_TestInvoice as p
    tmpl_TestInvoice.request = request
    tmpl_TestInvoice.session = session
    tmpl_TestInvoice.response = response
    tmpl_TestInvoice.serversetting = serversetting

    '' more code

    Add this after that section to override the filter set in the component

    '----------------- Add Filter -------------
    session.user_id = "00000005"
    tmpl.DBF.filter = "Customer_Id=\"\"" ' optional to set filter to a default
    if eval_valid("session.user_id") ' session.user_id exists
    if session.user_id """" ' value exists
    tmpl.DBF.filter = "Customer_Id=\""+session.user_id+"\""
    end if
    end if


    ' Result of above in interactive window
    'session.user_id = "00000005"
    'tmpl.DBF.filter = "Customer_Id=\""+session.user_id+"\""
    '?tmpl.dbf.filter
    '= Customer_Id="00000005"

    In this example, I set the session variable in the page code, but it may have been set elsewhere. That is the reason to test for both the existence of the variable and test if it has a value.

    Jerry

    Comment


      #3
      RE: WAS sessions variables

      Jerry,
      I set the filter as you recommended in the .a5w page. It does not appear to have any effect. I have tested for the session variable. It is present and returns a value. Did you actually get it to work?

      Thanks again for the reply

      Comment


        #4
        RE: WAS sessions variables

        John

        I use this technique on many pages and it works fine. Be sure that you have saved the page before previewing it. You may also want to close and reopen A5 to clear all of the session variables and saved queries and try again.

        Jerry

        Comment


          #5
          RE: WAS sessions variables

          Session variables can be cleared by stopping and restarting the Web Application Server, there is no need to shut down Alpha Five altogether.

          -Lenny

          Lenny Forziati
          Vice President, Internet Products and Technical Services
          Alpha Software Corporation

          Comment


            #6
            RE: WAS sessions variables

            Still cant' get this to work. I am unable to set a filter in an a5w page even without trying to call a session variable. I have started and stopped the server cleared cookies and placed the filter lines in various locations throughout the a5w file. I guess I'm about ready to pay for help. Any takers?

            Comment


              #7
              RE: WAS sessions variables

              John

              Attached is a zip file with a component and a a5w page using the component that shows how it works. These were created using AlphaSports. Unzip the files into the following folder under the A5V6 program folder.

              Samples\AlphaSports\Alphasports.WebProjects\Default.WebProject

              Open A5V6 and open Alpha Sports. You can open the Web Projects control panel and see how the component was built. If you look at the xbasic tab, you will see the syntax for the filter. Open the a5w page in the html editor and run the page. Note on the source code tab that the page has added a different fixed filter to the component. Then uncomment out the lines that set the session variable and see how the session variable is used in the filter and run the page again.

              You can use the same methods on any page to override any property set in the xbasic code in the component.

              Jerry

              Comment


                #8
                RE: WAS sessions variables

                Old dogs and morons can learn new tricks.

                Thanks Jerry

                Hope I can repay you some time

                Comment


                  #9
                  RE: WAS sessions variables

                  Jerry,

                  You da bomb!

                  I was almost completely out of hair when I tried your technique and it works like a champ!

                  From the example zip I realized that I needed to include the component name, then it was a snap.

                  Thank you for sharing your expertise!

                  Pat
                  Pat Bremkamp
                  MindKicks Consulting

                  Comment

                  Working...
                  X