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

.t. in query.filter not working

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

    .t. in query.filter not working

    I recall someone else mentioning this, but I can't find the thread.

    if I use .t. in a query filter I get the error field not found or similar
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    #2
    Why use .t. in filter expression?

    Martin,

    I don't use or need it for logical fields.

    Here's an example, using the logical "ship_same" field in the Customers table in AlphaSports:
    Code:
    tbl = table.open("customer")
    query.options = "M"
    query.order = ""
    query.filter = "Ship_same"
    qry = tbl.query_create()
    ?qry.records_get()
    = 52
    
    qry.drop()
    ?tbl.records_get()
    = 60
    And, for false, I'd use ".NOT. Ship_Same"

    -- t

    Comment


      #3
      my post was misleading, Tom. Sorry. I wasn't meaning like
      query.filter="somefield=.t."

      I meant
      query.filter=".t."

      I first saw this approach used by Alpha in V5. And it works in V5 and V6, but not in V7.

      I'm using it in a scnaio like this

      if such and such is so
      var->gpc="client_id='21'"
      elseif such and such is so
      var->gpc="client_id='22'"
      else
      var->gpc=".t."
      end if
      query.filter=gpc + " .and. city='boston'"

      I will have no problem programming around this - I'm just trying to confirm that I cannot use .t. in a filter, anymore.
      Cole Custom Programming - Terrell, Texas
      972 524 8714
      [email protected]

      ____________________
      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

      Comment


        #4
        I just ran a variation of your script in Alpha Sports in V7 and it worked as expected

        Code:
        if 1= 1
        	var->gpc=".t."
        else
        	var->gpc = "Bill_State_Region = \"MA\""
        end if
        query.filter=gpc + " .and. Bill_City='boston'"
        query.order = "lastname"
        
        tbl = table.open("customer")
        qdx = tbl.query_create()
        if qdx.records_get() = 0
        	ui_msg_box("","No records")
        	end
        end if 
        msg = ""
        tbl.fetch_first()
        for i =  1 to qdx.records_get()
        	msg = msg + tbl.lastname + crlf()
        	tbl.fetch_next()
        next
        	
        ui_msg_box("",msg)
        If I replace the 1=1 with 1=2, it also works as expected. However, I would typically use different syntax for the variable definition. Either dim the variable first or just implicitly define it in the script. For example, this would be one option.

        Code:
        delete gpc
        dim gpc as c
        
        if 1= 1
        	gpc=".t."
        else
        	gpc = "Bill_State_Region = \"MA\""
        end if
        query.filter=gpc + " .and. Bill_City='boston'"
        or I could just be lazy and implicitly define it.

        Code:
        if 1= 1
        	gpc=".t."
        else
        	gpc = "Bill_State_Region = \"MA\""
        end if
        query.filter=gpc + " .and. Bill_City='boston'"
        I don't think you need var-> in an implicit assignment.

        Comment


          #5
          took me a few minutes to figure this out, but as it turns out, the use of ".t." is not the issue.

          the issue is that the global variable [gpc] is losing its value
          I disabled all scripts except onkey
          I went to the interactive window and typed gpc="xxx"
          'gpc is a global vaiable
          and verified its value
          in the onkey event of the form i put
          msgbox("","" + gpc)
          end
          and it returned a value of "" (nothing)

          then, in oninit I added
          gpx="xxx"

          but got the same results
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            I can't duplicate the problem, but if you can send me files that allow us to duplicate the problem, we will investigate.

            Comment


              #7
              Martin,

              Just a thought. Check to make sure you are not declaring "gpc" someplace else as a local or shared variable. I have seen this result when this is the case.

              Scott

              Comment


                #8
                thank's Scott - no I was also declaring it in the onint event

                I found the problem. I have an embedded browse on the form
                at the canarrive event of the form, I say
                var->gpc=parentform.filter_get()
                this is resetting it to ""

                in the oninit event, I say
                gpc=".t."
                t=table.current() 'form based on one table
                query.filter=".t."
                query.order="labnum"
                t.query_create()
                t.fetch_first()
                browse1.refresh()

                and until I click in the embedded browse, it holds
                apparently, in V7, although the parent table is querried, the form's filter is still = ""
                I'm going to send it to Selwyn anyway, in case he sees any value to it.
                Cole Custom Programming - Terrell, Texas
                972 524 8714
                [email protected]

                ____________________
                "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                Comment

                Working...
                X