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

Conditional Style a little quirky?

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

    Conditional Style a little quirky?

    I'm using Conditional Style (Display Settings & Client Side Properties) pretty heavily in my grid. Up to about two releases ago, it was working beautifully. Then all went haywire. I read the release note about "true" & "false" as it relates to Client Side Properties. Mostly I get false - whether conditions warrant it or not. A "1=1" gives a solid true; using fields generally results in false (in spite of fact that field, displayed on the grid, yields true).

    For Display Settings Conditional Style, the first condition properly sets the Style. Subsequent conditions seem to take only **partial** effect. So if my second condition gives (Red, Bold) I will get Bold - but not Red (displayed text color is Blue). The first condition is (Blue, Normal.)

    For Client Side Properties Conditional Style, iif(1=1, "true", "false") seems always to give false. I think I got the format right, didn't I? It should always return true, shouldn't it? "1=1" gives solid true, even though it doesn't explicitly return the character string "true".

    Having trouble making sense of it all. I saw this some time ago - but it seemed to resolve itself (maybe it was a subsequent release). If anyone else experiences this in latest releases, I'd appreciate a reply.

    #2
    Re: Conditional Style a little quirky?

    Forgot to clarify - in the client side properties, it's the show/hide expression that I'm using the iif with (not so much the conditional style in the client side properties). But Show/Hide, too, seems to be on the fritz. The field is a link (not radio button, as mentioned in a recent release note).

    Comment


      #3
      Re: Conditional Style a little quirky?

      Forget the quotes...

      iif(1=1, "true", "false")

      iif (1=1,true,false)

      iif (if answer = 'Yes', true, false)

      The syntax in the help and examples is wrong.

      Check you are not using capitals e.g. True must be true
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #4
        Re: Conditional Style a little quirky?

        Originally posted by peteconway View Post
        Forget the quotes...
        The syntax in the help and examples is wrong.
        Well, ain't that just cheeky! Poor little idiot newbie, bashing his head against the wall, trying to get it to work as set forth in the product documentation, just to learn the documentation is wrong.

        Thanks, Pete. Now let's see if I can find a dent puller to pop that flat spot on my forehead. ;)


        P.S. It was the quotes.... I'd understood lower case was required. But there were the quotes, in the documentation, plain as day. And the very explicit instruction that you must return a "string". What's a guy to do?

        Comment


          #5
          Re: Conditional Style a little quirky?

          What's a guy to do?
          I hope you'll submit a formal bug report using the help menu in Alpha Five. Thanks. -- tom

          Comment


            #6
            Re: Conditional Style a little quirky?

            Bug was submitted 7 days a go, it will be corrected.
            Insanity: doing the same thing over and over again and expecting different results.
            Albert Einstein, (attributed)
            US (German-born) physicist (1879 - 1955)

            Comment


              #7
              Re: Conditional Style a little quirky?

              I had also seen inconsistency in the rendering based on my show/hide expression. Even though the expression returned the correct t/f value, the rendering would sometimes be properly affected, and other times not.

              In my field's show/hide expression iif(FieldVal > 0, true, false), where FieldVal was another field in the same row, the expression ALWAYS returned the correct result. This was easily proven by adding a column to the displayed grid and placing the expression result there. But sometimes I'd see a 'false', and yet the field would show. Or sometimes the reverse - a true result, but the field would not show as desired. The rendering results changed based upon selected number of rows to display. So if I displayed all rows, the results were perfect. But if I selected a number of rows to display that resulted in several "pages", ie: click NEXT to view the next page, the rendering was not reliable.

              This seems to have been resolved by latest patch
              Build 2515-3388 Oct-15-2009

              Comment

              Working...
              X