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

Changing Security Options for a Form

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

  • Changing Security Options for a Form

    This works in the IW as can be seen.
    [core] is the Form, [users] is the Group, [permission] is the table [Permission] is the Work Space.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    dim GID as C

    GID = a5_sec_get_gid("users","d:\AA_Alpha Five\Permission\permission.alb")
    ? GID
    = "f4c585d84d71484d8e19fbdc3a65eaf3"


    ? A5_Group_Has_Permission(GID, "core", "form", "delete", "grant")
    = "grant"
    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

    This has no effect on the permissions.

    A5_change_permission("users", "core", "form", "run", "deny", "password")

    I have tried using "GID" instead of "users", but the settings don't change.
    Also tried using the whole file path and "core.DDD".

    Any ideas where I am going wrong?
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    There are 3 things you can do in any situation;
    Live with it, Change it or Walk away from it.

  • #2
    Re: Changing Security Options for a Form

    A5_change_permission("users", "[email protected]", "form", "run", "deny", "password")

    if core is the name of the table which the core form is based upon.

    Name


    The name of the object and the data dictionary that contains it.

    (The example in the docs says "formname at tablename.ddd but that is wrong.)
    Last edited by Stan Mathews; 07-28-2017, 08:07 AM.
    There can be only one.

    Comment


    • #3
      Re: Changing Security Options for a Form

      "(The example in the docs says "formname at tablename.ddd but that is wrong.) "

      Well that's a few tries at various options down the tubes Stan. I suppose I should have trapped the "At" vs the "@"
      Much appreciate the correction.
      SQL seems a LOT easier!
      See our Hybrid Option here;
      https://hybridapps.example-software.com/


      There are 3 things you can do in any situation;
      Live with it, Change it or Walk away from it.

      Comment


      • #4
        Re: Changing Security Options for a Form

        Well I tried it and it does not work for me I'm afraid.
        This is what I used and I cannot fathom it out.

        >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
        A5_change_permission("users", "[email protected]", "form", "run", "grant", "password")

        dim GID as C
        GID = a5_sec_get_gid("users","d:\AA_Alpha Five\Permission\permission.alb")
        ? A5_Group_Has_Permission(GID, "core", "form", "run", "grant")
        = "deny"

        <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
        See our Hybrid Option here;
        https://hybridapps.example-software.com/


        There are 3 things you can do in any situation;
        Live with it, Change it or Walk away from it.

        Comment


        • #5
          Re: Changing Security Options for a Form

          When I tried a similar command to
          A5_change_permission("users", "[email protected]", "form", "run", "grant", "password")
          and then checked the form security it had changed.

          I did't try ? A5_Group_Has_Permission().
          There can be only one.

          Comment


          • #6
            Re: Changing Security Options for a Form

            Thanks Stan, but this is proving problematic.

            A5_Group_Has_Permission() does not appear when you try and enter this text in the IW
            A5_Has_Permission() does appear.

            The security does change, as you mention - but only on the first time it is run. Subsequent processes don't stick.
            (As an aside, it royally screws the Compact times, so something is "hanging")

            The A5_Group_Has_Permission() seems to be redundant.

            A5_Has_Permission() returns .T. in all cases, so I think that is busted too, unless my syntax is up the Swannie.

            All I am trying to achieve is a current value for the permissions on Forms and Tables, by Group
            There are three options for a Form; Run, Delete, Design.
            I am trying to get a simple and current list of Group Permissions to put in a Report.
            Viz:
            Group 1 can Run, 2 can Delete, 3 can Design.
            See our Hybrid Option here;
            https://hybridapps.example-software.com/


            There are 3 things you can do in any situation;
            Live with it, Change it or Walk away from it.

            Comment

            Working...
            X