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

Help with validation rule

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

    Help with validation rule

    I need help with a validation rule for a field called "Active" in a grid.
    This field can only be set to "Yes" or "No"
    When entering a new record, I would like a rule that checks to see if there is another record that has the value of "Yes" if so, return an error message.
    I am trying to warn the user if there is already a record that is set to "Yes".
    Thanks
    Tony

    #2
    Re: Help with validation rule

    Hi Tony,
    Is this something that can be done using the either the onFocus event for the "active" field,
    or the onBlur event of the field that sets the unique id you are using to lookup the active field?

    example : if this is based on whether or not an account is active, you would use something like
    Code:
    function eventname as c(e as p)
    dim errortext as c
    dim vargs as ::sql::arguments
    vargs.set("acct",<accountID>
    if sql_lookup(<connection>,"accountID=:acct","active",vargs) = "Yes" then
    errortext = "This account is already active"
    eventname = "alert('"+errortext+"');"
    else
    errortext = "No"
    end if
    end function
    You would need to use the e.pointer variable names where required, but I think this does the general task.
    Gregg
    https://paiza.io is a great site to test and share sql code

    Comment


      #3
      Re: Help with validation rule

      Gregg
      My field "active" does not have anything to do with an account being active or not.
      I use the field "active" to return an certain group of records from a table.
      So I could have used as an example a field named "switch_setting". The only two values permitted are "on" and "off" and I only want to permit 1 record at a time to be "on".
      When a user is enters a new record and they get to the field "switch_setting", I would like to check the table and alert the user if there is another record where the value of
      "switch_setting" equals "on".
      Thanks
      Tony
      Thanks
      Tony

      Comment


        #4
        Re: Help with validation rule

        Tony,

        We missed on something.
        I understand the "active" field can either be "Yes" or "No".
        The question is What is active , and what criteria are used to determine with it's active or not.
        Gregg
        https://paiza.io is a great site to test and share sql code

        Comment


          #5
          Re: Help with validation rule

          Depending on where the other record might be. It is either a loop through the grid or an Ajax-Callback.

          Comment


            #6
            Re: Help with validation rule

            I think we are getting closer.
            A company I work with has been in business for over 20 years.
            They have many customers that for whatever reason have not done business with them
            during the last 18 months. Those customers are marked as Inactive.

            A second example. I have a AAA membership.
            Last year, I chose to not renew.
            If I call AAA, I know they will say I have an Expired (inactive) account until I pay my membership dues.
            Gregg
            https://paiza.io is a great site to test and share sql code

            Comment


              #7
              Re: Help with validation rule

              I keep track of golf tournaments. When a tournament is on going, the field named "active" is set to "Yes"
              Once this tournament is over, it should be changed to "no"
              When a new tournament is being entered, the field active should be set to "Yes", but if the last tournament was not changed to "no" this causes problems

              Comment


                #8
                Re: Help with validation rule

                That's the answer I needed.
                The code below should guide you in the right direction,
                The event or action it takes to run the code depends completely
                on when you want it to make the announcement. Obviously, you can
                also set the value of Active, and eliminate the possibility of user error for this field.

                Code:
                function eventstatus as c(e as p)
                dim errortext as c
                
                if sql_lookup(<connection>,"active='Yes'","count(*)") >0 then
                errortext = "There is an active tournament"
                eventname = "alert('"+errortext+"');"
                else
                errortext = "No"
                end if
                end function
                Gregg
                https://paiza.io is a great site to test and share sql code

                Comment


                  #9
                  Re: Help with validation rule

                  Gregg
                  Thanks, I will give this a try!
                  Tony

                  Comment

                  Working...
                  X