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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Query filter

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Query filter

    In a query filer this works,
    query.filter = "po_number = var->vponumber"
    and this works
    query.filter = "supplier_id = var->vsupplierid"
    but this does not work
    query.filter = "po_number = var->vponumber.AND.supplier_id = var->vsupplierid"
    I need to use both tests in the filter. When I try the later I get an error "query.filter not logical expression"
    ?
    Thanks, Jeff
    Tags: None
    #2
    RE: Query filter

    Jeff,

    Check your dim statement, if any. Your var->whatever must be declared "further" than layout level. I just found this:

    NOTE: The query.filter expression cannot directly refer to Layout level variables on the form,
    or to form controls. Your script must set a local script variable to the value of the layout level
    variable, or the form control. Alternatively, declare variables on the form as Session level.
    For example, the following code does not work:
    query.filter = "state = which_state.value "
    Whereas, this code does work:
    state_to_query = which_state.value
    query.filter = "state = state_to_query"

    Hope this is your answer.

    Stan
    There can be only one.

    Comment

      #3
      RE: Query filter

      Jeff,
      In connecting one form with a filtered query to another form the line of code below worked for me. DEBTOR_NO and CLIENT_NO were filds on the table of the second form. FIELD1.TXT and FIELD.TXT were object values from the first form. Might be worth a try.

      layout_ptr:tables:cldebtor.filter_expression="DEBTOR_NO = '" + FIELD1.TEXT + "'" + ".AND. CLIENT_NO = '" + FIELD3.TEXT + "'"

      Comment

        #4
        RE: Query filter

        If you try the expression I showed you, cut and paste is better. The single and double quotes run together and look a little unclear on the message I left you.

        Comment

          #5
          RE: Query filter

          Hi Stan,
          This query is not at layout level. It is in a button script that uses
          t=table.open("ro_items")
          and so on to the query filter. The two fields that have to be tested against the two variables are in the ro_items table. What is puzzling me is that the filter will work when either is used by itself. I just can't seem to use the together in the same filter? By the way, one of them is character and the other is numeric. I don't think that would make any difference but who knows?
          Jeff
          PS, are you going to Boston in Dec?

          Comment

            #6
            RE: Query filter

            Stan, FYI I figured it out. This worked:
            query.filter = "val(supplier_id) = val(var->vsupplierid).AND.po_number = var->vponumber"
            It seems that a query.filter needs to have a constant field type. Once I converted the supplier_id field and vsupplierid variable to a numeric value all was well in scripting heaven!
            Jeff

            Comment

              #7
              RE: Query filter

              Hi Jeff,

              What you are trying to do should work. I think Stan is on the right track when he brought up variable scoping. You say your query is not at the layout level, but it appears that you are referencing variables at the layout level by your var-> syntax. Try getting the values in a local variable to the script such as: vstring = var->vsupplierid
              and vnumber = var->vponumber. Now use:

              query.filter = "po_number = vnumber.AND.supplier_id = vstring"

              If this doesn't work run debug(1) and put the variables in the debug watch variables and see what the value is as you step through the script.

              Good luck,
              Jim

              Comment

                #8
                RE: Query filter

                Hi Jeff,

                Glad you got it working.
                >>It seems that a query.filter needs to have a constant field type

                Comment

                  #9
                  RE: Query filter

                  Cool.

                  Hope to be in Boston. Have to wait on my boss to see.

                  Thanks for letting me know how you came out.

                  Stan
                  There can be only one.

                  Comment

                  Previous template Next
                  Working...
                  X