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

Cyber Security Webinar question: row level security - expression w/Arguments in sql select

  • Filter
  • Time
  • Show
Clear All
new posts

  • Cyber Security Webinar question: row level security - expression w/Arguments in sql select

    There was a question presented in the cyber security webinar yesterday about how to implement row level security. Certainly, on the client-side expressions can be used to show/hide or enable/disable controls. But when you are trying to hide the data from a user that has insufficient access rights to a particular row from the database then you might want the server to handle this instead of the browser. That way, there is no chance for the user to peek at the data by going to the html source on the browser.

    I have been trying to use the AlphaDAO "If" function in the SQL Select statement for my grids to accomplish this type of row-level field security. For example, if I want to display a static text string like, "-private comment-", when the current user is not the author of the comment then I setup a grid "argument" (:gUserID) that gets its value from a session variable and compares it to the author/owner ID in the record. The AlphaDAO sql would be like this:

    SELECT db.field1, db.field2, if( db.ownerid <> :gUserId, '-private comment-', db.cmnt) as dbCmnt FROM myTable

    I'm wondering if anyone else has tried this? And if you are able to use this method on grids that are part of the linked content of another grid? (At the moment I cannot select the child linking field when I try to link from my main grid.)

  • #2
    Re: Cyber Security Webinar question: row level security - expression w/Arguments in sql select

    Rich - I wonder about your syntax here.

    Here's a recent example from a List control SELECT statement I'm using, works well:

    SELECT ID, ActDate, Action, FollowDate, CASE WHEN Closed = 1 THEN 'Closed' ELSE 'Open' END
    FROM mytable
    It may be somewhat dependent on the back end, depending on portable SQL. This is MS SQL


    • #3
      Re: Cyber Security Webinar question: row level security - expression w/Arguments in sql select

      Switching my grid to native syntax, like you showed above (CASE-WHEN instead of IF()), causes all sorts of erroneous errors in the designer. The "if()" AlphaDAO syntax works for me in working preview; it just doesn't work if I include an Argument AND then try to include the component as a LINKed component on another grid. The backend does seem to make a difference as i cannot reproduce the problem with an Access 2007 database.