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

Limits to Lookups

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

    Limits to Lookups

    I have seen reference to people having problems with lookups. An application which has worked for several years is now causing me problems with respect to lookups.

    The fill field is a number but I display a character string. If I select from the dropdown list it insert the number an only shows the number. If I type the first character of the string it displays the string. The problem seemed to start after record XXX. Records above XXX do not seem to have the problem.

    The lookup is defined in the field rules. I am concerned that maybe the Table/set has too many lookups attached to it. Is that a possible problem?

    Thanks
    Truman
    Tags: None
    #2
    Re: Limits to Lookups

    Hi Truman,

    Originally posted by Truman View Post
    ....The lookup is defined in the field rules. I am concerned that maybe the Table/set has too many lookups attached to it. Is that a possible problem?
    I seriously doubt that any number of lookups would ever be a problem, as Alpha evaluates the code as it needs too. I'd look at the field rule definition for the lookup, any indexes of the lookup table and how it is being used.

    Good morning, and in case I don't respond later, good afternoon, good evening, and good night! ;) (Sorry, I just had to do that!)
    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

      #3
      Re: Limits to Lookups

      Hi Ira

      Thanks for the reply. I have found out that one of the tables in a set has quite a few lookup (over 50,000). The lookups are stored ID and displayed name. To open that table takes substantially longer than a similar table without lookups. (The lookup are fron another table and not a simple list with the items being defined in the field rules).

      I don't know if that makes a difference.

      Thanks and it is noon now.
      Truman

      Comment

        #4
        Re: Limits to Lookups

        Hi Truman,

        Originally posted by Truman View Post
        I have found out that one of the tables in a set has quite a few lookup (over 50,000). The lookups are stored ID and displayed name. To open that table takes substantially longer than a similar table without lookups. (The lookup are fron another table and not a simple list with the items being defined in the field rules).

        I don't know if that makes a difference.
        So we are not talking about the number of lookup definitions, but the number of records that a lookup is accessing. That is a different animal. If depends on how the lookup is being created. E.g., if it is using an index to pull the records it should be fairly fast, but if it is running a query (indicated by a progress bar when opening a form/browse or possibly entering the field), you might have to do it other ways.

        But there is not enough info to know what type and methods you are doing for the lookup. A sample with the field rule lookup giving a problem with a small lookup data table would be helpful to point you in the right direction.
        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

          #5
          Re: Limits to Lookups

          Originally posted by csda1 View Post
          Hi Truman,



          So we are not talking about the number of lookup definitions, but the number of records that a lookup is accessing. That is a different animal. ....

          But there is not enough info to know what type and methods you are doing for the lookup. A sample with the field rule lookup giving a problem with a small lookup data table would be helpful to point you in the right direction.
          Ok Ira you got me. Do you know anything about golf? I have been developing for myself a golf scoring program that tries to duplicate some of the features available in Game Tracker that Golf Channel and PGA Partners offer as a way to track you golf game. Now I do not want to share with you my golf scores (my golf is much worse that my limited Alpha programming skills). Let me see if I save further embarrassment by trying to explain what my program does.

          I have six tables that are linked to a parent table (call it gameID) which contains the date played the name of the player and the course played plus a couple other variables. This is the table is use to create a set which links to the six tables containing hole score; number of putts; length of drive; location of drive; sand save; and up and downs. Each table has a field for each hole some calculations related to the hole information � total score, total number of putts etc.

          The major lookups relate to the course being played, name of the player and the location of the drive (Left, Fairway, Right). In all cases I use a field rule which uses a table lookup with the link being the ID of the course, player or location; and displays the name of the course, name of the player or location (L, F, R).

          If there is a problem it is with location. Each game has 18 holes (fields) that use a lookup to the same tale and store the Location ID and display the location. I am playing around with either saving the location, rather than the ID, or making the field rule use a simple list which is defined for each field. It appears that either of these two approaches produces a location table that opens much faster than the original.

          Unfortunately my lookups of course and name are not working well (only two lookups per game). If there is a problem with having too many lookup, I am assuming that I probably have corrupted something and have to really clean up my program. I will probably copy half the records to a new database and see if the problem goes away.

          By the way I have tried to go back to Build 1847-3216 to see is the problem goes away. But the problem seems to exit with additional scores.

          Thanks and Good Night.
          Truman

          Comment

            #6
            Re: Limits to Lookups

            Hello Truman,

            Just a different take.

            Occasionally at work with 10 input operators, 2-3 like to go to the internet quite a bit.

            I too had problems with lookups, they would work perfect on one computer, and on the 2-3 other ones from time to time the lookups would not function properly. I guess If I did not have 10-15 computers to compare plus my own, I would not have guessed that the problem was a resource problem.

            Anyway on those computers, I usually run something like ad-aware or such first, do a disk clean-up, and a defrag with windows.

            Don't have all the technical answers, but it must be a resource clean up issue. After a reboot, Alpha usually settles back in, and in this case the look up that always worked once again work as promised.

            Not sure if that is the case here, but it will clean up your box a bit.

            Ed

            Comment

            Previous template Next
            Working...
            X