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

Table Lookup Help

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

    Table Lookup Help

    I have a field rule table lookup based on UK banking sortcodes which are a 6 number field with th following mask NN-NN-NN. However the lookup is suppose to order on this field also but it does not order correctly or find an appropriatly matching code.
    Is there a problem with lookups with masks and if so is there a workround.
    TIA
    Terry

    #2
    RE: Table Lookup Help

    I'm not sure what your message means, maybe it would help if you furnished more details.

    If you're having trouble 'finding' a record using the index to the 6 number field, you must be sure to use a key that matches the data format. If hyphens are embedded in the field by field rule, for example, you must insert the hyphens in the key used to 'find by key'. The opposite is true, too. If hyphens are not embedded in the field by field rule, then they must not be used in the key used with 'find by key'.

    -- tom

    Comment


      #3
      RE: Table Lookup Help

      Terry,

      I set up a test table with a table lookup on a field with phone number mask (555) 555-5555. It worked fine.

      I have had problems in the past with lookups when the lookup field is also an indexed field, and the index needed updating. Once I updated, it worked fine.

      You might check to see if the lookup table has your field in the indexes. If so, check that table to see if the records are sorting properly. If they aren't, update the indexes. If they display properly, but you're still having trouble, I'm not sure what's happening.

      Comment


        #4
        RE: Table Lookup Help

        There is a set in place and this is a lookup in a child dbf.
        It is a field rule table lookup with a popup on mismatch condition.
        A few examples of the entries are:-
        20-10-01
        21-33-45
        10-00-44
        It pops up every time even when the entry is correct.
        The pop up window does not show the records in the correct order and I cannot see what order it is using.
        It is not an index problem i have already checked this.
        Any help would be greatly appreciated.
        TIA
        Terry

        Comment


          #5
          RE: Table Lookup Help

          Is the field defined as 6 or 8 characters? One solution would be to define an index with the dashes removed (remspecial) then do a lookup with the remspecial. If it is an 8 character field with only a template, then the dashes aren't really there in the table. be sure that the field you are using to do the lookup is the same length as the field length in the table. If necessary, define a variable and pad it to be the right length before doing the lookup.

          Comment


            #6
            RE: Table Lookup Help

            Terry, can you post a zipped copy of the database?

            In the meantime...

            1) could the popup on mismatch be happening because of leading or trailing blanks which don't match?

            2) is the popup lookup list based on the same table which contains the lookup field, or is it a third table (other than parent and child in your set)?

            -- tom

            Comment


              #7
              RE: Table Lookup Help

              I would suggest checking the index you have selected in the lookup, Terry. My guess is that you forgot to specify the correct index when you set up the lookup in the field rules. It doesn't matter which index you have selected for data entry. It's the index you have selected for the lookup that governs how the information in the lookup database is ordered.

              Sylvia

              Comment


                #8
                RE: Table Lookup Help

                Thanks fo all the suggestions but I must confess I gave up by removing the masks on the field in both the parent and child tables. It now works fine.
                Terry

                Comment

                Working...
                X