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



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

Client Login with limited user rights

  • Filter
  • Time
  • Show
Clear All
new posts

  • Client Login with limited user rights

    Hi everyone,

    Quick question here on logins. My goal for my Web enabled alpha five database, is to allow a client to login via my webpage and view the information that I have stored under their client file. I have viewed the Login Feature tutorial that is shown on the Alpha website, but this seems more geared towards users logging in to use the entire database. I basically want to be able to have a client login, and view ONLY their information. I would also like them to be able to enter very basic information that will be stored in the database.

    What is the best way to approach this?

  • #2
    RE: Client Login with limited user rights

    I needed the same thing.
    Here is what I did. In the login AfterValidate I used the lookup function to set a session variable to the customer ID.
    Session._Protected_Cust_ID = lookup("[PathAlias.ADB_Path]\Customers","User_Name="+Quote(User_Name),"Cust_ID")

    Then I Created copies of the grid with a filter (Under the query tab of the grid)
    Cust_ID = 2000

    Then at the top of the webpage I set a case Statement:
    Case Session._Protected_Cust_ID =500
    tmpl_Soil_Search_Par = a5w_load_component("Soil_Sr_500")
    Case Session._Protected_Cust_ID =2002
    tmpl_Soil_Search_Par = a5w_load_component("Soil_Sr_2002")
    Case Session._Protected_Cust_ID =2004
    tmpl_Soil_Search_Par = a5w_load_component("Soil_Sr_2004")
    Case Session._Protected_Cust_ID =2005
    End select

    This way they can search and sort their record without seeing anyone elses work.

    Another way is to set the filter in the Components section of the page like this:
    with tmpl_Cust_Update
    componentName = "Cust_Update"
    end with
    '=======================================compute the HTML for the Component=======================================
    delete x_Cust_Update
    dim x_Cust_Update as p
    tmpl_Cust_Update.request = request
    tmpl_Cust_Update.session = session
    tmpl_Cust_Update.dbf.filter = "cust_id =" + Str(Session._Protected_Cust_ID,4,0)
    tmpl_Cust_Update.response = response
    tmpl_Cust_Update.serversetting = serversetting
    tmpl_Cust_Update.PageVariables = local_variables()
    x_Cust_Update = a5w_run_Component(tmpl_Cust_Update)
    This way they cannot search the record but they can see them.


    • #3
      RE: Client Login with limited user rights

      I missed something the After Validate is part of the Login dialog.
      I hope this helps.


      • #4
        RE: Client Login with limited user rights

        Thanks Jesse, your response did help me get done what I needed to get done. I was able to have client logins filtered by having their logon ID's be the same as their Client ID I assigned to them. However, I would like to have an "Admin" login that can view / search everyone's records, and maybe access some reports.

        Any suggestions on how to approach this? The way I have the filter work now is by setting a session variable out of the Client ID and then filtering it that way. Obviously if I have a login named "Admin" the way I have it working now will filter everything out, because clearly, "Admin" is not a client Id....


        • #5
          RE: Client Login with limited user rights

          I did a couple of things that might help:
          1: I set myself up in the customer database. What I did was use a logical field names admin: everyone else is set to false and I am set to true. then I pass it to a protected session variable in the after validate event:
          Dim session._Protected_IsAdmin as l
          session._Protected_IsAdmin = lookup("[PathAlias.ADB_Path]\Customers","User_Name="+Quote(User_Name),"Admin")
          In all the components that have administrative functions I bracketed all the components like this:
          "%a5 if session._Protected_IsAdmin then%"
          "td""%a5 ?x_Import_Results.Output.Body.Dialog_Echo %""/td""/tr"
          "td""%a5 ?x_Import_Results.Output.Body.Xbasic_Code_Errors %""/td""/tr"
          "td""%a5 ?x_Import_Results.Output.Body.Dialog_HTML %""/td""/tr""/table""br"
          "%a5 end if %"
          So that even if a person hacked into the site they would only see the outline of the page but no components.

          Then I gave in each of the data pages my own unfiltered component. Again bracked off so that only an administrator can see it.
          I hope that helps.