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

Security Settings

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

  • Security Settings

    Is there any way to give someone the rights to run operations but not do design layout changes? It looks like operations that change information (appends, imports, etc) are tied into the "design" security options. I trust people to run operations but not with the layouts!

  • #2
    An off-line source recommend using a custom toolbar that didn't have the design button on it. This would prevent people from accidentally getting into the design. It would still be accessible on the control panel, in a place less apt to be accidentally accessed. If anyone else has any suggestions, please let me know!

    Comment


    • #3
      Assuming you are using Alpha Five's built-in security model, all you have to do is set the Design permission to Deny on layouts and the Run permission to Grant.
      Aaron Brown
      Alpha Software Development Team

      Comment


      • #4
        I tried doing that, but "design" is connected to operations that import, append, etc. With "run" you can do queries, but operations that change data won't run without "design" being given. At least when I tried it, this is how it worked. I don't see a separate "layout" option, just "design."

        Comment


        • #5
          Layouts are forms, browses, and reports. They have separate security settings. Maybe I am confused at what you are trying to do.
          Aaron Brown
          Alpha Software Development Team

          Comment


          • #6
            I want employees to be able to run operations that append, import, export, etc., but don't want them to be able to make design layout changes in forms. With run, you can run reports, queries, etc., but not operations that actually change information (append, import, export, etc.) which appear connected to "design". If I give them "design" rights, I'm afraid someone will alter the form's design (e.g., change a field name, move the form in the grid, etc.) It seems like these type operations would be a "change record" item, but they don't appear to be. I hope this makes sense!

            Comment


            • #7
              Originally posted by twebb
              I want employees to be able to run operations that append, import, export, etc., but don't want them to be able to make design layout changes in forms. With run, you can run reports, queries, etc., but not operations that actually change information (append, import, export, etc.) which appear connected to "design". If I give them "design" rights, I'm afraid someone will alter the form's design (e.g., change a field name, move the form in the grid, etc.) It seems like these type operations would be a "change record" item, but they don't appear to be. I hope this makes sense!
              I think there is fundamental misunderstanding here...Permissions are assigned on an object-by-object basis. Giving someone run or design rights to a form or report has no effect on their permissions to an operation.

              Operations don't have records, and neither do reports or forms, thus only tables have change record permissions.
              Aaron Brown
              Alpha Software Development Team

              Comment


              • #8
                Maybe I am totally missing something! I know you can set security individually on forms, and also on the control panel. What I am doing is right clicking on the control panel, choosing "set security" and looking at the options. In form, you only have design, run and delete options from what I see under set security, the control panel gives more options, which is why I am using it.

                All I know is that if I don't give someone "design" rights, they can't run my append, export, import operations, but if I do, they can. But if I do, they can also get into design and move objects around in the forms themselves.

                What am I missing?!

                Comment


                • #9
                  What are you setting design rights on? The table, the operation, the form? If you right click on whitespace on the operations tab, you are setting permissions for all operations, but NOT layouts. If you right click on whitespace on the forms tab, you are setting permissions for all forms, but NOT operations or any other class of object. A permission is specific to whatever object you are operating on. If you right click on an individual operation and set design permission, that is separate from any other object. Table rights are completely separate from operation rights or layout rights.

                  To summarize, if you set permissions for "My Operation", it has no effect on the permissions for "My Form."

                  Have you read the documentation at support.alphasoftware.com on the security model and it's hierarchical nature?
                  Aaron Brown
                  Alpha Software Development Team

                  Comment


                  • #10
                    Aaron, thank you very much for giving me this last bit of information. I was working from the manuals and the class I took, and just wasn't aware of permissions by object. I'm sure this'll do the trick. Thank you for your patience! Tina

                    Comment

                    Working...
                    X