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

Login Session Variables

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

    Login Session Variables

    I have created a "login" in page as described in "Create a Login Page" and it works fine. I have three fields in my "Users" table Users_name, Password and Account#. The "results" page that the user is taken to after validation shows all the information for all the users. We need the grid to show only the information for the logged on users account. The account# field is the link between the two tables.

    Is there a way to pass in account# field from "login" table to the "results" page to show only those transactions?

    Any help on this would be great!

    Marlene

    #2
    If you search on filtering session variables, you will find a number of discussions which address exactly what you are trying to do.


    Originally posted by marlenel
    I have created a "login" in page as described in "Create a Login Page" and it works fine. I have three fields in my "Users" table Users_name, Password and Account#. The "results" page that the user is taken to after validation shows all the information for all the users. We need the grid to show only the information for the logged on users account. The account# field is the link between the two tables.

    Is there a way to pass in account# field from "login" table to the "results" page to show only those transactions?

    Any help on this would be great!

    Marlene

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

    Comment


      #3
      Marlene:

      If you get stuck let me know. I can walk you through the process. It is fairly straight foward.

      Steve

      Comment


        #4
        That would be wonderful.....there are so many messages posted out there under "filtering session variables" it is mind boggling!!

        Comment


          #5
          OK


          Step one:Following the examples Alpha provides in the log in dialog, make sure you use the lookup function to retrieve the values you need to build your filter. It sounds like the account number in your case is the key.

          Step two:

          Set a session variable which holds your filter statement in the dialog component that you are using to log in. You can declare this is the validate event section. See example:

          Code:
          session.filter="staff_name="+Quote(staff_namev)+ ".AND. update=" + "{" + session.master_datev + "}"
          The names ending in v are variables and staff_name and update are field names in a table. In this case the logged on user will only see records that match a name and a date requirement. Your string may look different depending on the data types of your variables.

          Once this session variable is set you need to add code to the A5w page that holds the grid component. If you look at the source you will see somthing similiar to what I have posted below. This area allows to override the grid's properties. In this case, the grid (your page) will filter based on the filter you set in the login dialog.


          Code:
          Delete tmpl_Results
          DIM tmpl_Results as P
          tmpl_Results = a5w_load_component("Results")
          'Following code allows you to override settings in the saved component, and specify the component alias (componentName property).
          'Tip: Keep the componentName property short because this name is used in page URLs, and it will help keep the URLs short.
          'Each component on a page must have a unique alias (componentName property).
          with tmpl_Results
          	componentName = "Results"
          	
          	 'check if session.state exists
          if eval_valid("session.filter") = .t. then
          'check to see if the component already has a filter. if not
          'then set the filter, if so, then append the filter to the existing filter
          if dbf.filter = "" then
          dbf.filter=session.filter
          else
          dbf.filter=session.filter
          end if
          end if
          componentName = "results"
          end with 
          
          
          '=======================================compute the HTML for the Component=================

          If you have everything set up properly, when your user logs in and you pass them to the appropriate page they will only the records as designated by your filter. Let me know if you need anything else. Good luck!

          Steve

          Comment


            #6
            Steve,

            I was wondering about this part of your code:
            if dbf.filter = "" then
            dbf.filter=session.filter
            else
            dbf.filter=session.filter
            end if

            Comment


              #7
              I understand where to put the last code, but I'm not sure where I am suppose to use the lookup function and set the session variable. Do I do this in my Arw pages or in my Web Component pages? Also, does it matter which section I put these statements in?

              Comment


                #8
                Hi:

                Look at the sample log in Alpha uses. That particular component that takes the user supplied variable and checks it against the database to ensure username and password are correct is the one where you will set the session variable in the events section - validate or after validate section. The lookup is used to grab the account number if that is the data that keys into the filter. The code below is from the Alpha Web demo login dialog component.

                Code:
                if user_name = "" .or. password = ""  then 
                	currentform.has_error = .t. 
                	currentform.error_message = "User name or password cannot be blank."
                else
                	dim correct_password as c 
                	DIM level AS N
                	
                	correct_password = lookup("[PathAlias.ADB_Path]\user_names","user_name=" + quote(user_name),"password")
                	if correct_password = password then
                		level = lookup("[PathAlias.ADB_Path]\user_names","user_name=" + quote(user_name),"level")
                		session.__protected__SecurityLevel = level
                		session.WASDemo.UserName = user_name
                	ELSE
                		currentform.has_error = .t. 
                		currentform.error_message = "Invalid user name or password."
                	end if  
                end if
                Once the username and password have been confirmed you can use similiar code to pull out the account number and set that to a session variable. That variable will then be used in your filter statement that is also declared in this area. Hope this helps - if not let me know.

                Comment


                  #9
                  Ed:

                  I most likely stole some code that had an alternate filter established and instead of deleting the added statements and doing it the correct way, I just cut and pasted the filter designation so that my condition was met.

                  Steve

                  Comment


                    #10
                    Steve,

                    I will try this ASAP. Thank you very much for all your help!!

                    Comment

                    Working...
                    X