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

User Permissions for a Button

  • Filter
  • Time
  • Show
Clear All
new posts

  • User Permissions for a Button

    Is it possible to only allow certain users to click a button on a form that runs an on-click script? I know I can set it up so you have to enter a password on a button before it will run the script, but I'm trying to avoid making the approved users type in a password every time they click that button.

    The purpose of this button is to clear information from specific fields. I only want our managers to be able to click the button, so that our sales support staff can't accidentally click the button and delete data that shouldn't be deleted.

    Any help is appreciated.

  • #2
    Re: User Permissions for a Button

    You could put the button on a conditional object and set it so that only the appropriate users ever see the button, much less push it. You could also have the default for the button to be disabled and if certain users are logged in the button gets enabled.
    There can be only one.


    • #3
      Re: User Permissions for a Button

      Don't have this version, but if you go to Advance Search and type in "password", "user password" or just about any variation of this you will find a lot of discussions. Don't know if you find the answer to your request about specific fields, but Stan's idea looks promising, or look at the link below. A5 has a built in program. I think it can be done, just a little work to set one up.


      • #4
        Re: User Permissions for a Button

        Stan's Idea works great. I use that one a lot in many applications.
        Dave Mason
        Skype is dave.mason46


        • #5
          Re: User Permissions for a Button

          We keep a table of users and their permission levels. Using that table and methods like Stan has described, we can allow/restrict access to many different types of objects. We've been doing it for years.


          • #6
            Re: User Permissions for a Button

            Stan's method works well. Just remember you can't have a conditional field within a conditional field as this kills Alpha.
            I also use this to disable features a customer hasn't paid for, but rather than hide the button I display a greyed out version with either no events attached or onpush set to display a message describing the missing functionality. Have had a couple of add-on sales using this approach.


            • #7
              Re: User Permissions for a Button

              Just remember you can't have a conditional field within a conditional field as this kills Alpha.
              Jon, This is not true. I have c in c in c in c. I have seen where others do this as well.
              Dave Mason
              Skype is dave.mason46


              • #8
                Re: User Permissions for a Button

                Dave - I'm impressed. Always causes a serious crash or loop when I try it both on reports and forms.


                • #9
                  Re: User Permissions for a Button

                  I do it in forms and reports as needed. No problems
                  I have one form that has 4 levels of cond objects. reports with up to 3 levels.
                  All need to have different conditions of course.
                  Be careful the edges don't flow over of course.
                  Dave Mason
                  Skype is dave.mason46


                  • #10
                    Re: User Permissions for a Button

                    Wow - this could make my life a little easier. Wonder if it was just my installation or a general issue which Alpha fixed, but always had serious problems with overlapping or nested conditional fields.


                    • #11
                      Re: User Permissions for a Button

                      I have been using this since v7


                      Last edited by DaveM; 10-02-2015, 01:58 AM.
                      Dave Mason
                      Skype is dave.mason46