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 Object on a Report/only1 condition recognized?

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

    Conditional Object on a Report/only1 condition recognized?

    I thought this would be simple, but I am stumped.

    I am trying to have conditional text print on a report. I have placed the conditional object on the report (which I have done many times on other reports)...but this time I have the expression set to look for 2 conditions. (Filenum="c044".and.type$"mass")- This does not show the text as I expected.

    If I just leave it at Filenum="c044", the text will print. I have tried moving parentheses, no parentheses, every combination I could think of, but it will never print when I add .AND.(the rest). My expression always evaluates to L no matter which way I try to set it up, but it still does not print.

    So can you only have 1 condition in the expression in the object on a report ?

    Thanks for any input.

    #2
    Re: Conditional Object on a Report/only1 condition recognized?

    is "type" a variable ?

    If so, change the variable name to something else. "Type" is a reserved word.

    Comment


      #3
      Re: Conditional Object on a Report/only1 condition recognized?

      "Type" is not a variable - it is the name of the field

      Thanks Tom

      Comment


        #4
        Re: Conditional Object on a Report/only1 condition recognized?

        Tell us about the type field in table structure and supply sample values that might be found within it.

        Have you verified that your expression returns true?

        Comment


          #5
          Re: Conditional Object on a Report/only1 condition recognized?

          We do inspections on homes. The "type" field identifies what type of inspection was ordered. That field is located in our "inspections" table. It is a character field, 35 characters long. Examples of types are "Home", "Pest", "Pool", etc.

          The expression in a conditional object on all the reports I do evaluates to "False" meaning I get the:

          Results:False
          Type: L

          at the bottom of the expression builder box. My other conditional objects have always worked correctly with the box stating such?!

          The report is built on a set that includes the inspections table - in case you were going to ask that next !!!

          Comment


            #6
            Re: Conditional Object on a Report/only1 condition recognized?

            Terri, you may be foregetting the trailing blank spaces that are part of every Type field.

            It's not accurate to say that your field values are "Home", "Pest", "Pool", etc.

            If you could see the blanks your field values would be:

            "Home____________________"
            "Pest_____________________"
            "Pool_____________________"

            I think your expression should trim trailing blanks and having done that I'm wondering why you use the substring inclusion operator? Is "mass" a complete string or a substring of some larger string of characters?

            Getting details from you is like pulling teeth. Why don't you take a few minutes and tell us exactly what this expression is doing (or should be doing) ? without sparing any details.

            Thanks.

            Comment


              #7
              Re: Conditional Object on a Report/only1 condition recognized?

              Like I first said, this was supposed to be simple.

              I have report and I want a conditional text statement to print on it if the file is connected to a specific client AND a specific type of inspection.

              If the report refers to that specific client and type, the text should show "Do not inspect the crawl space"

              The client number is "C044"
              The type of inspection is "home"

              I put my report in design mode. I use the choose the conditional object from the toolbox and place it on my report. I go into the properties and click on Condition Expression. I choose my fields - ClientID - I make it "=" "C044" - I click on .AND.
              I choose the field "Type" click on "$" and enter "home" (I used the "$" because "home" can refer to the type "Home TX" or "Home Destination" or just plain "Home")

              So my expression in the expression builder looks like

              Client->Client_Id="C044".AND.Type$"home" ( I have also attached a screen shot)

              I label it, click on OK and my conditional object shows on the report. I right click on it, choose properties, bring focus to my labeled layer. I place a text box in the area, type in "Do not inspect the crawl space" and save it.

              I find a record that matches my conditional criteria and print the report I have just changed and the text DOES NOT print.

              HOWEVER, if I just leave the conditional expression as

              Client->Client_Id="C044" It WILL print the text on the report.

              This is not what I need because if we send out the report to do a pool inspection I cannot have "Do not inspect the crawl space" show on the report.

              Hence my question "Is only 1 condition recognized?"

              Comment


                #8
                Re: Conditional Object on a Report/only1 condition recognized?

                ok, thanks.

                I think I see the issue. You're using the substring inclusion operator ($) backwards.

                Type $ "home" will be true only if the string of chars in the type field are contained in "home". I think you want the reverse.

                "home" $ Type, which will be true only if the string "home" is found within the current type field value.

                So, try this:
                Code:
                client->client_id = "C044" .and. "home" $ Type

                Comment


                  #9
                  Re: Conditional Object on a Report/only1 condition recognized?

                  OK - imagine revelation music in the background.....

                  do you hear the singing........ "Amen and Allelujah" ????

                  That did it! THANK YOU !!

                  Comment


                    #10
                    Re: Conditional Object on a Report/only1 condition recognized?

                    Hey, I can hear the music ! That's great!

                    Comment

                    Working...
                    X