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

An .OR. between betweens

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

    An .OR. between betweens

    I aam wondering if lightning query optimization ca happen in a form query if I have a filter that looks like the following:

    between(orderstatus,"1","3") .OR. between(orderstatus,"5","7")

    Some people say that optimization can happen with AND/OR/NOT links and some people say otherwise.

    #2
    RE: An .OR. between betweens

    This is from the book.
    The condition expression must use operators that are compatible with Lightning Query Optimization. These include:
    ? Equals (=)
    ? Exactly equals (==)
    ? Greater than or equal to (>=)
    ? Greater than (>)
    ? Less than or equal to ()
    ? BETWEEN(..)
    ? SMATCH - see note below
    ? Wildcards (* and ?) - see note below
    ? .NOT.
    ? .AND.
    ? .OR.
    NOTE The SMATCH function and the wildcards * and ? can only be used with LQO if they appear at the end of the expression. For example, a search for McC* can be optimized since the wildcard operator appears at the end, while a search for *stein cannot be optimized, since the wildcard operator begins at the beginning.
    Partial Compatibility
    In some cases, only part of your query's selection expression can be used with Lightning Query Optimization. In this case, Alpha Five applies the optimization algorithm to the compatible part, and uses Alpha Five's standard query algorithm to evaluate the rest.
    For example, suppose you have a table of customers for which you have created an index that sorts records by the field City. You then create a query which uses the following selection expression:
    (CITY = "BOSTON").AND.("Commonwealth" $ ADDRESS1)
    Because the second half of the expression uses an operator that is not compatible with LQO and a field which is not used in a pre-existing index (ADDRESS1), Alpha Five applies Lightning Query Optimization to only the first part of the expression.
    Furthermore, in cases where the selection expression evaluates to TRUE for most of the records in the table or set, Alpha Five may analyze the query and determine that Alpha Five's standard query algorithm is more suitable. In this case Lightning Query Optimization is not used.

    Comment


      #3
      RE: An .OR. between betweens

      Greg,

      I have not done extensive testing of version 4.5 or version 5, but I can tell you that version 4 did not seem particularly clever in it's ability to use LQO.

      I'm guessing, but I believe that the .OR. operator would not be used. As far as I can tell, A5 V4 looked for a portion of an equation that would allow it to effectively set a begin and end of a range of an index that would minimize the number of records that it needed to look at. In your case, it had 2 sections of the index that it would need to get, and I don't believe it was smart enough to do it.

      This is an area that I'm sure has constant tinkering by Alpha Software, and thus may change significantly from version to version and even maintenance release to maintenance release. The guideline I use is to present the equation (by building an equation in a character string -assuming it is dynamic) that is already simplified. For example, for your case(and assuming only integer numbers are valid), I would get the minimum and maximum values (1 and 7) and present the equation as such

      between(orderstatus,"1","7").AND..NOT.(between(orderstatus,"4","4"))

      Alternatively,

      between(orderstatus,"1","7").AND..NOT.(orderstatus=="4")

      The way I can tell for sure is that I actually run queries and test for the length of time that it takes to process (using NOW() function). Note that NOW() has a resolution of about 1/18th of a second, thus it is possible for the difference results to be off by as much as .12 seconds. This means that if your entire length of query is dealing with a small number, it is hard to tell if the numbers are faster or slower. Finally, you must force the query to always evaluate (or delete the query results). If not, A5 sees that it was previously run, and doesn't even run it the 2nd time.

      Regards,

      Ira J. Perlow
      Computer Systems Design & Associates
      [email protected]
      Regards,

      Ira J. Perlow
      Computer Systems Design


      CSDA A5 Products
      New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
      CSDA Barcode Functions

      CSDA Code Utility
      CSDA Screen Capture


      Comment


        #4
        RE: An .OR. between betweens

        Thanks Ira I have reconfigured my queries to reflect your suggestions it will be interesting to see how things turn out as the database grows. I am a little lost on what you mean by reevaluating the query. The user in my case presses a button to access the form and the query is invoked I had thought that when the form is closed the query is closed. If this is not the case how do you go about reevaluating the query?

        Comment


          #5
          RE: An .OR. between betweens

          Thanks for pointing this out. I just don't understand why Dr. Peter Wayne indicated in his book "Xbasic for Everybody" in chapter 20 Queries section that "for optimization to take place, the query filter can only reference one table, and the query expression cannot use the conjunctions .and., ,or., or .not..

          Comment

          Working...
          X