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

Case Statement in Expression Builder

  • Filter
  • Time
  • Show
Clear All
new posts

  • Case Statement in Expression Builder

    Does any one have any idea why this CASE Statement will not work in the Expression Builder?

    Here's what I am trying to accomplish:

    Each person can have a Prefix (Mr. Mrs. Dr...), a First Name, a Middle Name, a Last Name and a Suffix (Jr, Sr).

    I am trying to create a calculated field (Full Name) in the field rules of the table in question.

    The problem is that some people do not have a middle name and some do not have a suffix.

    Here's the beginning of the expression I am trying to build...

    case(isblank(Middle_Name).AND.isblank(Suffix),alltrim(Prefix)+" "+alltrim(First_Name)+" "+alltrim(Last_Name),isblank(Middle_Name).AND.isnotblank(Suffix),alltrim(First_Name)+" "+alltrim(Last_Name)+" "+alltrim(Suffix))
    Any insight would be most appreciated.

    Kindest Regards,

    Last edited by Louis Nickerson; 08-23-2009, 08:00 PM.

  • #2
    Re: Case Statement in Expression Builder

    Louis -

    I know someone else will help with the expression, so I'll leave that alone.

    But a hint that might help:

    When you have an expression that's relatively complex, but you can't make work, build a function in XBasic to do the work. That's easier to trace/debug, gives you plenty of room for your logic, etc. A big time-saver over trying to keep your eyes focused on this kinda thing.


    • #3
      Re: Case Statement in Expression Builder

      May be better off with an if statement. try

      If(isblank(Middle_Name).AND.isblank(Suffix),alltrim(Prefix)+" "+alltrim(First_Name)+" "+alltrim(Last_Name),IF(isblank(Middle_Name).AND.isnotblank(Suffix),alltrim(First_Name)+" "+alltrim(Last_Name)+" "+alltrim(Suffix),""))

      What that attempts to to is

      If(statement1 is true,Result,If(statement2 is true,result,"")) - Blank if both statements are false


      • #4
        Re: Case Statement in Expression Builder


        Thank you for your reply.

        I did notice that I'm missing a closing parenthesis in the expression, but that isn't what is causing the problem.

        I am an avid proponent of writing functions and agree that things can be better evaluated in that environment.

        My concern is that the expression builder doesn't seem to be handling even the most basic of expressions. Sure, if I specify a field name, it works, but if I try to make it conditional using a "case" or "if" statement, it just treats me like I'm nuts. Maybe I am...but I could swear I've done this in the past with no problems.

        Thanks again !



        • #5
          Re: Case Statement in Expression Builder

          Originally posted by Louis Nickerson View Post
          Does any one have any idea why this CASE Statement will not work
          It is not the case statement.
          When using isblank() or isnotblank(), you need to enclose the fields' names in quotation.

          And as an aside (or two).. this case() statement could be slimmed and trimmed and shuffled around for much better efficiency. But that's a long story and the subject of a whole new thread.


          • #6
            Re: Case Statement in Expression Builder


            Thank you for your response.

            I prefer "If" statements to the Case function. I know that case is easier to code, but for me at least, it's easier to decipher a nicely written IF statement.

            That being said, My first attempt at this was using an IF statement very much like your example.

            I even tried your statement (see the attached screen shot) to no avail.




            • #7
              Re: Case Statement in Expression Builder

              Using the the ifblank you must encase the firld with quotes - "field name". It wil not work if you do not.


              • #8
                Re: Case Statement in Expression Builder


                Well, color me embarrassed !

                I have been using CASE for years and never run into this. I guess even at my old age, we can still learn something every day.

                Thanks to all who replied.



                • #9
                  Re: Case Statement in Expression Builder

                  It happens in the best families.
                  Unlike most, why this particular functions require fields in quotation?
                  Somebody had a vendetta or a bad hair day.
                  Last edited by G Gabriel; 08-23-2009, 08:26 PM.


                  • #10
                    Re: Case Statement in Expression Builder

                    I agree...the requirement for field names to be quoted is odd.

                    Oh well, they have to do something to keep us on out toes.

                    Thanks again for your help.


                    • #11
                      Re: Case Statement in Expression Builder

                      Hey Gabe,

                      You just made me a Certified Alphaholic. Thanks, was it good for you?


                      • #12
                        Re: Case Statement in Expression Builder

                        Yes.. but I don't like this alphaholic thing.. I have enough mental problems I don't need any more.