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 expression

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

    Help with Validation expression

    In Validation tab, usually the expression entered in the "Value of an expression must be unique" box is a combination of 2 or more fields like fieldA+fieldB+etc..
    In my case I would like to enter an expression like: FieldA + isnotblank(FiledB). A5 won't accept this sort of syntax. So my question is: how to get A5 to consider duplicates when 2 records have the same value in Field A and both records have any value in Field B. The rule being: if 2 or more records have the same value in Field A, only one of them is allowed to have a value (any value) in Field B.

    #2
    Re: Help with Validation expression

    You'll probably have to script the field rule cansaverecord event to check for other entries..

    Looks like you can have a uniqueness test and a custom validation. Might be doable with a combination.
    Last edited by Stan Mathews; 02-18-2009, 03:58 PM.
    There can be only one.

    Comment


      #3
      Re: Help with Validation expression

      For the "Value of an expression must be unique" expression use an if() function.
      Pick a field or combination of fields (primary key) that will always be unique. Lets say an autoinc called Recid.

      Make the expression: If(isblank("FieldB"),Recid,FieldA)

      This will cause the value to be compared to be that of Recid if FieldB is blank. Since this value is already unique it basically cancels out the validation rule. If FieldB is not blank then it simply returns the value in FieldA of which there can only be one.

      You may need to enter this for FieldB as well. If fieldA is always entered first then fieldB will probably always be blank so you would need the validation to trigger when FieldB is given a value. This starts to look like you probably want to use the custom validation section anyway so you can give appropriate messages to the user.
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


        #4
        Re: Help with Validation expression

        Hi Tim:
        Thanks for putting me on the right track. I modified your IF statement as follows: IF (isnotblank(FiledB), FieldA, .T.); as mentioned previously 2 or more records may have the same value in Field A. However, only one of them is allowed to have a value (any value) in Field B. The above expression seems to work as desired in the "Value of an expression must be unique" section. Now, I am trying to move it to the custom validation section so I can give the user a message but having a hard time turning the IF() statement into a logical expression. If you could help me turn the above IF statement into something the Custom Validation section would accept, it would be fantastic.
        Thanks Tim

        Comment


          #5
          Re: Help with Validation expression

          Don't know when I can get back to take a look at it but if some one else hasn't got you sorted before I can I will be happy to look further. In the mean time you might give some more details of fields involved, type,size etc. And best of all would be a sample with some test data for us to work with.
          These pages may be of help
          http://support.alphasoftware.com/alp...tion_Rules.htm
          http://support.alphasoftware.com/alphafivehelpv9/Functions/KEY_UNIQUE().htm

          The expression you are using now doesn't look right to me. Any record that has FieldB as blank would return .T. (which would only make sense if fieldA is also a logical) So if there are multiple records with FieldB as blank then there should be multiple '.T.' values which would not be unique.
          Tim Kiebert
          Eagle Creek Citrus
          A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

          Comment


            #6
            Re: Help with Validation expression

            I don't see how your expression can work as isblank() and isnotblank() both require doublequotes for the field used such as

            Code:
            IF (isnotblank([COLOR=Red]"[/COLOR]FiledB[COLOR=Red]"[/COLOR]), FieldA, .T.)
            In addition is your field called "FieldB" or "FiledB" ??
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment


              #7
              Re: Help with Validation expression

              Hi Mike:
              Sorry for the confusion, these are just typos.

              Comment


                #8
                Re: Help with Validation expression

                Tim:
                Thanks for the Key_unique() function; it helped a lot, problem practically solved.

                Comment

                Working...
                X