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

Show/Hide Expression

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

    Show/Hide Expression

    Hi Guys...

    Having trouble with an expression to show a button when the COVERAGE value is not one of "GL" or "PROP". I've tried a bunch of ideas and so far only a single expression works:
    Working single Ex.:
    coverage<>"GL"

    Some other attempts:
    coverage<>"GL" or "PROP" (doesn't really evaluate if GL and PROP are selected.

    not(coverage="GL" or "PROP")
    not(coverage like "GL" or "PROP")
    coverage<>"GL" and coverage<>"PROP"

    Any ideas or help would be appreciated.

    Thanks
    Joe
    Never take a ride to the edge of your mind unless you've got a ticket back - Jon Oliva - Savatage.

    #2
    Re: Show/Hide Expression

    Is the expression used in Alpha?

    .not. (coverage="GL" .or. coverage="PROP")

    coverage<>"GL" .and. coverage<>"PROP"

    .not. inlist(coverage,"GL","PROP")
    There can be only one.

    Comment


      #3
      Re: Show/Hide Expression

      Yes, the expression is used in Alpha on a Grid but according to the syntax rules xbasic is not allowed.

      .not. (coverage="GL" .or. coverage="PROP")

      coverage<>"GL" .and. coverage<>"PROP"

      .not. inlist(coverage,"GL","PROP")

      I've tried:
      not(coverage="GL" or coverage="PROP")...didn't work
      not(coverage="GL") or not(coverage="PROP")...didn't work
      coverage<>"GL" or coverage<>"PROP"...didn't work
      (coverage<>"GL")or(coverage<>"PROP")...didn't work
      not(coverage="GL")...didnt' work - figured I'd try singular evaluation

      I'm just not getting it...even for the evaluation to occur their seems to be a lag.

      Joe
      Never take a ride to the edge of your mind unless you've got a ticket back - Jon Oliva - Savatage.

      Comment


        #4
        Re: Show/Hide Expression

        What about
        Code:
        coverage<>"GL"  .or. coverage<>"PROP"
        Or maybe you need to insert the field twice in the editor Like:
        coverage<>"GL"
        coverage<>"PROP"
        Dan

        Dan Blank builds Databases
        Skype: danblank

        Comment


          #5
          Re: Show/Hide Expression

          Hi Dan...

          Thx for the reply...

          .or.
          .and.
          .not.

          cannot be used according to the syntax rules on the show/hide expression builder. I tried your suggestion earlier and it errors out as it has no logical operator. I'm pretty confident that some of the one's I've tried should have worked but they haven't so I'm not sure if it is a bug, poor documentation and I'm missing something...or what???

          Stumped...
          Joe
          Never take a ride to the edge of your mind unless you've got a ticket back - Jon Oliva - Savatage.

          Comment


            #6
            Re: Show/Hide Expression

            Hi

            I understood, the buttons only show when coverage is neither GL nor PROP? I tried the following expression that worked for my grids:

            Code:
            coverage<>'GL' and coverage<>'PROP'
            according to the doc, single or double quotes can be used so this detail should not make any diff.

            regards

            Comment


              #7
              Re: Show/Hide Expression

              It must be valid Javascript which is case sensitive. Does the status line show any javascript errors ?
              https://appsbydesign.co.uk/

              Comment


                #8
                Re: Show/Hide Expression

                That works perfect...I don't under stand why "and" would work and not "or". Doesn't make sense...test users now told me they could pick GL and PROP from the list. When I do that the button appears and it shouldn't so I guess I really need it to be "not one of" or "not in". Sorry and thanks for the help.

                Joe
                Never take a ride to the edge of your mind unless you've got a ticket back - Jon Oliva - Savatage.

                Comment


                  #9
                  Re: Show/Hide Expression

                  Joe

                  You are right. Something is wrong. I tried

                  Code:
                  (coverage <> 'GL' and coverage <> 'PROP')
                  and it works, but the logical equivalent
                  Code:
                  not(coverage = 'GL' or coverage = 'PROP')
                  does not.

                  I would say this is a bug.

                  Comment


                    #10
                    Re: Show/Hide Expression

                    This isn't a bug. It's the nature of testing for inequality with a logical OR.

                    The truth table for a logical OR is

                    1 OR 0 = 1
                    0 OR 1 = 1
                    1 OR 1 = 1
                    0 OR 0 = 0

                    So ...

                    if Coverage is 'GL' you get
                    Coverage <>'GL' =0
                    Coverage <>'PROP'=1

                    0 OR 1 = 1 or true so display

                    if Coverage is 'PROP' you get
                    Coverage <>'GL' =1
                    Coverage <>'PROP'=0

                    1 OR 0 = 1 or true so display

                    if Coverage is HOME' you get
                    Coverage <>'GL' =1
                    Coverage <>'PROP'=1

                    1 OR 1 = 1 or true so display

                    So the net result is the expression always equates to true.

                    Since you are testing for inequality the logical OR will return true in all conditions presented.

                    A logical OR works fine when testing for equality as it should. When testing for inequality a logical AND makes sense.

                    BTW .. the expressions entered in show/hide are not pure Javascript. It's a hybrid language, looks like a cross between Xbasic and Javascript to me. They are converted to Javascript which you can check by viewing the source sent to the browser.
                    Bob Moore


                    Comment


                      #11
                      Re: Show/Hide Expression

                      Bob

                      That's not what I am saying. I said that

                      Code:
                      (coverage <> 'GL' and coverage <> 'PROP')  does work (I tested it)
                      not(coverage = 'GL' or coverage = 'PROP') does not work although it is the exact logical equivalent.
                      in the second expression,
                      Code:
                      if coverage = 'GL', then we have
                      not(1 or 0) = not (1) = 0 ==> button should hide
                      if coverage = 'PROP', then we have
                      not(0 or 1) = not (1) = 0 ==> button should hide
                      if coverage ='xyz' we get
                      not(0 or 0) = not (0) = 1 ==> button should show
                      So it is a bug

                      Comment


                        #12
                        Re: Show/Hide Expression

                        Wolfgang,

                        Sorry for the confusion, I was trying to explain the logical OR and I didn't look closely at your example.

                        Code:
                        not(coverage = 'GL' or coverage = 'PROP')
                        You are correct that logically this should work.

                        When you open the browser and look at the source code Alpha is generating you can see that the Javascript is:

                        Code:
                        if( (!COVERAGE == 'GL' || COVERAGE == 'PROP') == true ) showHide = '';
                        	else showHide = 'none';
                        So the generated code is not what I would expect.
                        Bob Moore


                        Comment


                          #13
                          Re: Show/Hide Expression

                          Originally posted by Bob Moore View Post
                          Wolfgang,

                          Sorry for the confusion, I was trying to explain the logical OR and I didn't look closely at your example.

                          Code:
                          not(coverage = 'GL' or coverage = 'PROP')
                          You are correct that logically this should work.

                          When you open the browser and look at the source code Alpha is generating you can see that the Javascript is:

                          Code:
                          if( (!COVERAGE == 'GL' || COVERAGE == 'PROP') == true ) showHide = '';
                          	else showHide = 'none';
                          So the generated code is not what I would expect.
                          Bob

                          thanks for digging into this :=)) I fully agree with you. That is not the conversion one would expect. The '!' needs to go outside of the inner brackets....

                          Anyway I do not understand why Alpha does not use pure javascript for the syntax here...

                          Thanks and kind regards

                          Wolfgang

                          Comment


                            #14
                            Re: Show/Hide Expression

                            Just curious...did anyone try
                            not(coverage = 'GL') or not(coverage = 'PROP') ?? This, to me, seems to be the equivalent to the and script.
                            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


                              #15
                              Re: Show/Hide Expression

                              Originally posted by MikeC View Post
                              Just curious...did anyone try
                              not(coverage = 'GL') or not(coverage = 'PROP') ?? This, to me, seems to be the equivalent to the and script.
                              it seems not to be the equivalent.

                              if coverage='GL', we have
                              not(1) or not (0) = 0 or 1 = 1 ==> Button would show, which is not what was required and is therefore not the equivalent. However, you could put
                              Code:
                              not(coverage = 'GL') and not(coverage = 'PROP')
                              if coverage='GL', we have
                              not(1) and not (0) = 0 and 1 = 0 ==> Button would hide
                              if coverage='xyz' we have
                              not(0) and not(0) = 1 and 1 = 1 ==> Button would show

                              regards

                              Comment

                              Working...
                              X