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

Using .AND. & .OR. in a Query Filter

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

    Using .AND. & .OR. in a Query Filter

    I'm putting together a script and having a problem with the use of .AND and .OR. in a query filter. If I remove the ".OR." statement from the filter, the query works perfectly. If I insert the ".OR." statement, it returns records for only the ".OR." criteria, and ignores the other criteria in the query. Obviously A5 does not like to see both in a query filter. Below is my script so far:

    dim tbl as P
    dim tbl1 as P

    tstr1 = ui_get_text("Client Name","Please Enter Client")
    if tstr1=""then
    end
    end if
    user1=(tstr1)

    dstr = ui_get_date("Date Received","Please Enter Date In")
    if dstr=""then
    end
    end if
    user2=ctod(dstr)

    tbl=table.open("ameregl3")
    tbl1=table.open("tasks")

    'debug(1)

    tbl.change_begin()
    ameregl3->job = tasks->tasks
    tbl.change_end()

    'tbl=table.current()

    query.description = ""
    query.order = ""
    query.filter = "AMEREGL3->ATTORNEY=(user1).AND.AMEREGL3->DATE_IN=(user2).AND.ameregl3->code=\"cd\".OR.ameregl3->code=\"adne\""
    query.options = "I"
    tbl.query_create()

    Even though I'm not declaring that "(user1)" and "(user2)" are variables, the script works perfectly without the .OR. statement. As soon as the .OR. statement is added it only filters for that part of the filter. Any ideas for a workaround, or another way to state the filter? I thought perhaps a "CASE" statement might work but am unsure of how to put it together. Also, a CASE statement here would probably return true or false and I don't think that would work either. Thanks for reading the post.

    #2
    Re: Using .AND. & .OR. in a Query Filter

    3 words for you. algebra - boolean logic

    query.filter = "AMEREGL3->ATTORNEY=(user1).AND.AMEREGL3->DATE_IN=(user2).AND. (ameregl3->code=\"cd\".OR.ameregl3->code=\"adne\")"

    I'd also suggest that you use debug(1), the trace window, or a messagebox to show the value of query.filter
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      Re: Using .AND. & .OR. in a Query Filter

      THanks Al..... I'll give it a try...but.... I sucked at Algebra....lol.

      Comment


        #4
        Re: Using .AND. & .OR. in a Query Filter

        Thanks loads Al, that was the ticket. You rock and definitely something else to file away for future scripting......Thanks again,
        Scott

        Comment


          #5
          Re: Using .AND. & .OR. in a Query Filter

          I find it likely that you are coding this for a button on a form based on a set where amergl3 is the parent and tasks is the child. If this is so.......

          Code:
          tbl=table.curent(1)
          tbl1=table.current(2)
          
          'debug(1)
          
          tbl.change_begin()
          tbl.job = tbl1.tasks
          tbl.change_end()
          prentform.refresh()
          It will be confusing later, or would to me, to revisit code that mixes form methods such as

          ameregl3->job = tasks->tasks

          and table methods such as

          tbl.change_begin()
          There can be only one.

          Comment


            #6
            Re: Using .AND. & .OR. in a Query Filter

            Among other reasons why Al "rocks" is that he's spent a bit of time looking at the help file documentation. The examples in topics "Logical .and." and "logical .or." illustrate the importance of grouping terms with parentheses when appropriate. Recommended.

            Comment


              #7
              Re: Using .AND. & .OR. in a Query Filter

              Originally posted by draxx View Post
              THanks Al..... I'll give it a try...but.... I sucked at Algebra....lol.
              We are living in the most practical example of an Algebra world when we work with software and databases.

              For sum this is more fun than Math class. Of course no one here had me for their Math instructor.
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein

              http://www.iadn.com/images/media/iadn_member.png

              Comment


                #8
                Re: Using .AND. & .OR. in a Query Filter

                Thanks Tom

                Comment

                Working...
                X