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



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


  • Filter
  • Time
  • Show
Clear All
new posts


    I am trying to learn more about LQO and it is still fuzzy in my head. In the help file there is just 1 page that talks about what you need to have before you can use LQO, but not not how to use it. I did a search and found this:
    Originally posted by csda1 View Post
    TableMax() can do the same thing, IF the filter expression can invoke LQO with an index,
    What I don't get is: is LQO a process that A5 automatically starts when the conditions it needs are met or is it something that the user has to programatically or manually starts?
    Referring to the above quote, how do you get the filter expression in Tablesum() to invoke LQO? I don't see an option in the syntax that says use LQO or don't use LQO.
    Thanks in advance.

    Re: LQO

    LQO works when a query expression matches an index expression. They need to be an exact match. And the help doc tells you what functions are best to use.

    If your index expression is this:

    then make sure your LQO expression is something like this:

    alltrim(CustomerID) = YourKeyHere

    That help?


      Re: LQO

      Originally posted by gaby_h View Post
      I am trying to learn more about LQO and it is still fuzzy in my head. In the help file there is just 1 page that talks about what you need to have before you can use LQO,

      Originally posted by gaby_h View Post
      but not not how to use it.
      Not so much.

      Lightning Query Optimization is a feature that Alpha Five activates to increase the speed at which queries are run.
      To take advantage of this time-saving feature, both the query you design and the pre-existing indexes must be compatible with Lightning Query Optimization.
      Originally posted by gaby_h View Post
      how do you get the filter expression in Tablesum() to invoke LQO
      The filter expression must take advantage of existing indexes and use the operators outlined in the documentation.

      A query consists of a filter expression and/or an order expression. Any time you use a filter expression, Alpha runs a query.
      There can be only one.


        Re: LQO

        Yes it's more clear now,... just to make sure I understand this:
        If I have an index by State, a query/filter using the expression State > "FL" would use LQO, whereas a filter expression like Amount > 100 won't?

        Thanks guys.


          Re: LQO

          Hi Steve,

          Originally posted by Steve Workings View Post
          LQO works when a query expression matches an index expression. They need to be an exact match.
          That's not quite correct Steve. It does not have to be a match, but needs to match the beginning field(s) of the index expression.

          I have placed similar up to date info in my LQO tips area for future thread viewers.

          LQO (Lightning Query Optimization) is a process that essentially happens automatically whenever you apply any filter or query to a table (except for the filter inside an index definition). It creates a dynamic range to an index. Back in Alpha Four, (and actually is still doable in Alpha Five), you might do a search (query) by setting a range that reduced the number of records that needed to be searched.

          E.g. If you wanted only people whose last name began with P, your range for an index whose expression was LastName+FirstName would be "P" through "Pz". Alpha would only access those "P" records.

          In order to be more generic than a range, LQO takes a part of the expression of the filter (e.g Between(LastName,"P","Pz) and looks to see if there is an index that uses the field of that part of the expression at the beginning of the index expression. It then tries to set a range that restricts the range of records that need to be accessed, and then applies the filter to only that record. So if your filter expression was
          (FirstName="Ira") .and. Between(LastName,"P","Pz)
          then ideally it would search the records only starting with "P".

          Unfortunately, LQO isn't super intelligent. You need to help it a bit to find a matching index. It is best that the beginning part of the filter expression that you want to match to an index rearrange the filter terms to either start with a matching equality (or >= or <=) statement or use a Between() with constants for the 2nd and 3rd arguments, as in
          Between(LastName,"P","Pz) .and. (FirstName="Ira")
          LastName="Perlow" .and. FirstName="Ira"
          So for a last name search, Alpha Five would be just as happy with index expressions of
          It may not work with
          LQO will not help (and could slow it down a bit) if the range of selected records is a large percentage of total records. This is not typical, but happens if you create filter and index expressions incorrectly.

          When you get the LQO right, your speed of accessing records for large tables will increase a lot. That's the only way to really tell if LQO is happening (unfortunately it would be nice if Alpha had an LQO evaluator which would show you when it would actually happen)
          Last edited by csda1; 10-28-2009, 01:27 PM.

          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