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

Is there a quicker way?

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

    Is there a quicker way?

    Hi

    I have a filtered lookup set up on a sports statistics table. The filter works fine in showing only those records from an external table for players who are eligible to play in the game for which statistics are beeing entered. BUT it is slow!

    The filter looks for players who are entered for the year the game takes place and also appear on either of the teams registrations for that year. The expression (shown below) is entered in the field rules for the table and every time the registration number is entered into the table the filter then "sweeps" through the tables 3 times to generate the lookup. This takes time and results in an unhealthy pause before proceeding.

    Is anyone able to point me in the right direction to speed this up?

    Regards

    Glen Schild

    ---------------------------------------
    (teamkey+(str(year(Registrationdate),4))=rushing->hometeamkey+(str(year(rushing->gamedate),4))).or.(teamkey+(str(year(Registrationdate),4))=rushing->visitorteamkey+(str(year(rushing->gamedate),4)))
    Glen Schild



    My Blog


    #2
    RE: Is there a quicker way?

    Glen,

    Unfortunately the use of the "or" operator means the query will not optimize.

    Have you created indexes based on the exact expressions of the lookups? Wouldn't hurt.

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: Is there a quicker way?

      Bill

      Thanks for the response. I must admit I am not sure I understand. Unless I have misunderstood you, to create indexes for the expression in the lookup would mean to create one for each game? This would be impractical as there are over 160 games in any one season.

      I am figuring that it is going to come down to a trade off between performance and data accuracy. Before trying this method of forcing data accuracy I used a calculated field hidden on the form which appeared in Bright Red when an error was made in data entry. Guess I might have to revert to this!

      Regards

      Glen
      Glen Schild



      My Blog

      Comment


        #4
        RE: Is there a quicker way?

        Glen,

        You don't need an index per game. I was thinking about indexing expressions such as:
        rushing->hometeamkey+(str(year(rushing->gamedate),4))).

        Queries run faster when there is an underlying index with the same structure. Certain query expressions can benefit from LQO. Look it up in the manual.

        While you are at it replace
        (str(year(rushing->gamedate),4)
        with cyear(rushing->gamedate)

        which can only speed things up as it eliminates a function from the expression.

        Finally, it is sometimes a good idea to add a field to your
        table (which you fill automatically with a calculate field rule) and index the calculated field so queries can optimize.

        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: Is there a quicker way?

          Bill

          Thanks, the calculated fields did the trick, now the lookup is almost instantaneous.

          Regards

          Glen
          Glen Schild



          My Blog

          Comment

          Working...
          X