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

Prevent Changes on a form

  • Filter
  • Time
  • Show
Clear All
new posts

  • Prevent Changes on a form

    How do I prevent changes on a form depending on the value of a field.
    I have tried using the forms can change event but this seems to fire when you fetch a record, whereas I am seeking to trap at a point the user tries to change a record.
    Too many fields to add individual rules for each field.

  • #2
    Re: Prevent Changes on a form

    You might try using the "restrict_change" property of the form.

    For example, in the onsave event for the form you might set the restrict_change property of the form to TRUE if the value in your field warrants it.

    In the onFetch event of the form you would set it TRUE if the value in your field warrants it, otherwise you'd set it FALSE.

    It might be smart to include a hotspot or a password protected button so an administrator can release the restriction in appropriate cases.


    • #3
      Re: Prevent Changes on a form

      "Depending on the value of a field"
      Are the fields you want protected a specific value, or a seeded value you want protected?
      How would you identify non updatable fields?
      Ted Giles
      Example Consulting - UK

      See our site for Alpha Support, Conversion and Upgrade.


      • #4
        Re: Prevent Changes on a form

        OnInit OnActivate events

        check the field value - set the topparent.Allow_change to .f.

        You may want to add it to the determining fields onchange or the form's onsave event to change it after the field is changed or saved.
        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.


        • #5
          Re: Prevent Changes on a form

          Your suggestions worked perfectly.
          Thanks Tom.


          • #6
            Re: Prevent Changes on a form


            Glad that works for you.

            Depending on the complexity of the application, you may need more checking than that.

            Even in a single user system, a posting field rule or some thing else can change a value through another process.

            Field rules and object events are triggered by some type of user interaction. So you have to be careful about what does and doesn't trigger your test.

            The single 'catch all' type of event is the ontimer event for the form. Then you can have a re-evaluation of the rule on a timer.

            It all depends on complexity your application faces.

            The allow_change I suggested gives the option of F3 to undo the flag and allow changes.

            Tom's restrict_change option is tighter, but doesn't allow F3 to undo it. You could have a button/menu/toolbar option to do that.

            The OnKey event allows you to test every key stroke.

            Many options - choose wisely... and test test test

            Doesn't mean you'll catch it in time unless you have a very short time interval.
            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.


            • #7
              Re: Prevent Changes on a form

              Thanks Al
              Lots of good advice there, some will be adopted.


              • #8
                Re: Prevent Changes on a form

                Tried using the form as a dialog or tool?
                or as a modal window?
                Dave Mason
                Skype is dave.mason46