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

Lookup will show all records, not the wanted

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

    Lookup will show all records, not the wanted

    I have a form with a browse and I want to get records in the browse that matches another table.
    See Attached Sample:

    The form name:Orderform
    In the brose in that form there is the field Repname is a lookup based on the field repcode.

    It should only show the records matching the repcode. It shows all the records.
    2 questions 1: Why?
    2: Was this the best approach, or should I have taken a different, more direct approach right from the orderform?

    The obective was to add a repname with a matching number in the main form to the browse.

    #2
    Re: Lookup will show all records, not the wanted

    In the lookup definition for the repname field set the filter to Codex = producttable->repcode
    Tim Kiebert
    Eagle Creek Citrus
    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

    Comment


      #3
      Re: Lookup will show all records, not the wanted

      Mike

      I don't understand what you are trying to do.

      I read your explanation and can't follow the steps.

      Too many pronouns - it is what?

      ....Or just let Tim figure it out......
      Al Buchholz
      Bookwood Systems, LTD
      Weekly QReportBuilder Webinars Thursday 1 pm CST

      Occam's Razor - KISS
      Normalize till it hurts - De-normalize till it works.
      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
      When we triage a problem it is much easier to read sample systems than to read a mind.
      "Make it as simple as possible, but not simpler."
      Albert Einstein

      http://www.iadn.com/images/media/iadn_member.png

      Comment


        #4
        Re: Lookup will show all records, not the wanted

        Thanks for responding.

        Codex = producttable->repcode
        Tim, that was the code needed to complete this long process, now it works.
        Thanks

        Al or some one perhaps could add, if my approach about selecting the rep could have been more efficient or quicker.

        There were too many steps

        1 Create a global variable
        2 I had to assign the value of repgroup from the ordertable to a global
        3 create 3 events to transfer values: a-oninit b-on ftech c-onexit to clear
        4 add a field in the producttable to hold the productgroup like 2000 or 6000
        5 In the field rules of the producttable transfer the value of the global to the repcode.
        6 create the lookup in the field repname.

        My Quad Intel processor was huffing and puffing after all that coding.
        Was there a shorter approach?
        Last edited by MikeData; 01-19-2011, 08:36 AM.

        Comment


          #5
          Re: Lookup will show all records, not the wanted

          I eliminated your steps 1-5. removed all traces (i think) of the global variable. removed the repcode field from the producttable and embedded browse.


          1/ add an index to the ordertable on orderno. ( this index will probably not go to waste anyway.)
          2/ create the lookup in the field repname. using a modified filter of Codex = lookupc("F",producttable->Orderno,"repno","ordertable","Order_")

          This filter is looking up the repno from the ordertable using the current orderno (producttable->Orderno) as the link. It then compares that value to Codex.
          Last edited by Tim Kiebert; 01-19-2011, 11:40 PM.
          Tim Kiebert
          Eagle Creek Citrus
          A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

          Comment


            #6
            Re: Lookup will show all records, not the wanted

            Tim that is perfect. What a lesson!
            I am sure is also cleaner, efficient and slick.
            Thanks.

            Comment

            Working...
            X