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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Restrict access to certain fields

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Restrict access to certain fields

    I need to know how I go about giving an employee restricted access to change only certain fields in a form. We are an Insurance Brokerage Firm and currently have about 250 fields in our form - I would only like them to be able to change a handful (21) of these fields. Is this possible? How do I go about doing it? We are currently using A4V6? I also thought about upgrading to A4V8, other than being more windows friendly, are there any benefits that would help my current situation?

    Thanks.
    Karla
    Tags: None
    #2
    RE: Restrict access to certain fields

    2 things come to mind.

    1. Create a form that contains only the 21 fields that the user can change.

    2. Create a form with 229 calculated fields (250 - 21). You can't change a calc field on a form.

    P.S. My email address is now: [email protected]

    Comment

      #3
      RE: Restrict access to certain fields

      By doing this they would have to go between the 2 forms to make changes right? If that is the case that wouldn't work for us. I want them to be able to view everything all on the same form. Let me know if I'm not understanding correctly.

      kn

      Comment

        #4
        RE: Restrict access to certain fields

        A possible better solution is to edit the database's field rules and set the Skip Field field rule to .T. for all fields that you do not want them to edit. This will prevent the cursor from landing on those fields. It also eliminates the need for a custom form. It will work with the default form as well as all custom forms.

        Comment

          #5
          RE: Restrict access to certain fields

          Karla

          A. Do you want a form that some employees can change all the fields and other employees can only change the 21?

          B. Do you want the other 229 fields to be changeable on another form(s)?

          Just want to be sure about what you want done.

          I doubt that a4v8 would help in this case. V7 made A4 work in the WIN 2000 and XP environment and uses windows printers for standard printing. V8 adds email and faxing.

          A5v5 adds a user level security system that would make choice A. easier to implement. (Amoung other things)
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment

            #6
            RE: Restrict access to certain fields

            Yes that is what I need. 2 users would be able to access all 250 fields and the rest would only be able to change the 21 fields.

            The previous idea would work perfect if I could password protect it, so the 2 authorized users can change the info on the form.

            kn

            Comment

              #7
              RE: Restrict access to certain fields

              Unload the attached can_edit.zip file into its own folder. The TEST.DBF database contains 1 record. Look at the field rules for the name and address fields. They are skipped if the CANEDIT variable is "Y". Next, run the TESTAPP application. Select Open Form A or Open Form B. You are promtped for a password. Type SMITH and press ENTER twice. Select Change from the menu bar and the cursor will stop at every field. Press M to go back to the Mainmenu. Select Open Form A or Open Form B. If you leave the password blank or type in something other than SMITH (or smith, it's not case sensitive), the cursor will skip the name and address fields and will only go to the phone number fields. Finally, look at the 3 scripts, PWGET, PWPROMPT and PWFORM. The password SMITH is stored in a file named PASSWORD.VAR. To change the password, simply edit that file and change it. I recommend you rename the file to something besides PASSWORD.VAR. I named it PASSWORD.VAR for illustration purposes only. If you rename it, you will also need to modify the filename in the PWGET script. The can_edit2.zip file is the same as can_edit.zip with the exception of the PWPROMT script. I hide the password by making the text color the same as the background color.

              Comment

                #8
                RE: Restrict access to certain fields

                Here's the can_edit2.zip file.

                Comment

                  #9
                  RE: Restrict access to certain fields

                  Let's try that again.

                  Comment

                  Previous template Next
                  Working...
                  X