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 Next Higher/Lower value

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

  • Lookup Next Higher/Lower value

    In a lookup the options are First/Last/Closest. However I want A5 to return the next higher value. For expl if the value being looked up is 510 and Source table goes by 50 (450, 500, 550, 600,...), I want A5 to return 550. Is there a way to twist the Lookup() function to return the next higher or lower value?
    Thanks

  • #2
    Re: Lookup Next Higher/Lower value

    No. Use a different value to lookup.


    Instead of whatever holds the "510", say a variable "someval"

    lookup

    if(mod(someval,50)>0,(int(someval/50)*50)+50,someval)

    and use first for the higher value (than 510) to be returned.
    There can be only one.

    Comment


    • #3
      Re: Lookup Next Higher/Lower value

      Hi Stan:
      Thanks for the reply.
      What do I do in cases where the values don't go up by a fixed amount, like in postal rate tables, tax tables?

      Comment


      • #4
        Re: Lookup Next Higher/Lower value

        For returning the next higher value the lookupn() function should be what you want. It uses an index and when you specify closest it finds the next closest value after it passes the supplied value.

        Given a table "arates" (index named "wt" created on lbs field)

        Code:
        LBS	RATE
        1.50	7.10
        2.90	8.40
        3.60	9.10
        4.10	12.60
        4.70	15.00
        ? lookupn("C",4.111,"rate","arates","Wt")
        = 15
        There can be only one.

        Comment


        • #5
          Re: Lookup Next Higher/Lower value

          Gaby, this looks like something that could be handled using a User Defined Function which you would roll yourself. i.e. it's time to create your own lookup() function.

          Comment


          • #6
            Re: Lookup Next Higher/Lower value

            Next Higher value:
            Lookup(Table,round_up(your_number/5000,2)*5000,expression)
            Next Lower value:
            Lookup(Table,round_down(your_number/5000,2)*5000,expression)
            Last edited by G Gabriel; 10-28-2008, 06:01 PM.

            Comment


            • #7
              Re: Lookup Next Higher/Lower value

              Originally posted by gaby_h View Post
              What do I do in cases where the values don't go up by a fixed amount, like in postal rate tables, tax tables?
              Simple:
              For Next Higher value:
              lookup(table,">=your_number", exp)

              For Next Lower value:
              lookup(table,"<=your_number", exp)

              These should work whether the incremental value is fixed or not which makes the suggestion I gave in the previous post look stupid. I could have deleted that previous post and spared myself the embarrasment, but I decided to leave it for research purposes in case someone ponders how evolution takes place.
              Last edited by G Gabriel; 10-28-2008, 06:18 PM.

              Comment


              • #8
                Re: Lookup Next Higher/Lower value

                G, I agree with your next higher... but wonder whether you've actually tested the next lower approach... I'm not sure that will work.

                Comment


                • #9
                  Re: Lookup Next Higher/Lower value

                  True.
                  Good thing I kept the previous post.
                  Last edited by G Gabriel; 10-28-2008, 07:32 PM.

                  Comment


                  • #10
                    Re: Lookup Next Higher/Lower value

                    Here's a more general solution, relying on a custom UDF to do the heavy lifting.

                    -- tom

                    Comment


                    • #11
                      Re: Lookup Next Higher/Lower value

                      Here is a UDF for the next lower value:
                      Code:
                      FUNCTION Lookup_Next_Lower AS N (tablename as c, filter as c, result_expression as c)
                      	x=table.external_record_content_get(tablename,result_expression,result_expression,filter)
                      	Lookup_Next_Lower=val(word(x,-1,crlf()))
                      END FUNCTION

                      Comment


                      • #12
                        Re: Lookup Next Higher/Lower value

                        Tom, your solution looks great but I tried a number of things and can't get passed the expression builder, keep getting <invalid or incomplete expression>. Could you please show how the expression should look in the expression builder with the following example:

                        Source table: p_rates
                        field: Weight (index: Bywt)
                        field: Postage

                        Current table: Transactions
                        field: Quantity (index: Qty)
                        field: Cost ---> is a calc field = LK_Next(......... , ..........., ........ , ......... , ........)
                        Thanks

                        Comment


                        • #13
                          Re: Lookup Next Higher/Lower value

                          Code:
                          LK_next("p_rates",1.45,"ByWt","H","Postage")
                          = 0.59
                          "p_rates" is the source table name, in quotes

                          1.45 is the numeric weight, no quotes

                          "ByWt" is the name of index based on the Weight field in source table, must be in quotes

                          "H" means next "H"igher, in quotes

                          "Postage" is the name of the source table field containing the numeric value to be returned, quotes


                          In this example the source table "P_rates" is searched for a record with weight equal to 1.45. It returns the postage value from the record containing the next higher weight. Or it returns zero if there is no higher weight in the table. In my sample the "next higher weight" is 2.0. The "postage" for weight of 2.0 is 0.59.

                          Comment


                          • #14
                            Re: Lookup Next Higher/Lower value

                            I see, so the value to be looked up (1.45) has to be hard coded in the expression, I was using the field's name (Quantity) instead of a value.
                            I thought A5 would take whatever value entered in a transaction table in Quantity field (1.45), goes to Source table looks up the Next Lower/Higher value in Weight field, grabs the rate (0.59) in Postage and inserts it in Cost field in Target table.

                            Comment


                            • #15
                              Re: Lookup Next Higher/Lower value

                              Perhaps the UDF needs to be tweaked. I'll be happy to check it. Post your database and point me to the calc field rule you're trying to define.

                              Later...

                              No tweaking required. Works as advertised. The value to be looked up does NOT have to be hard coded. Check the calc field rule expression for the "t_postage" field in the new "transactions" table I've built.

                              ===================================================================
                              Source table: p_rates
                              field: Weight (index: Bywt)
                              field: Postage

                              Current table: Transactions
                              field: Quantity (index: Qty)
                              field: Cost ---> is a calc field = LK_Next("p_rates",Quantity,"ByWt","H","Postage")


                              -- tom
                              Last edited by Tom Cone Jr; 10-29-2008, 02:35 PM.

                              Comment

                              Working...
                              X