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 within a calculated field expression

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

    LOOKUP within a calculated field expression

    When I write this expression for a calculated field the expression builder tells me that the following expression is invalid:

    Amt_used * LOOKUP("components", "Prim_Comp=components->Comp_Num", "Cost_per_unit")

    "Amt_used" and "Prim_comp" are valid field names in a table named "material_usage". When I simply change the field name of "Prim_Comp" to "Comp_Num" and make the expression:

    Amt_used * LOOKUP("components", "Comp_Num=components->Comp_Num", "Cost_per_unit")

    It evaluates perfectly. Do the field names in separate tables need to match for the lookup to work properly?

    #2
    Re: LOOKUP within a calculated field expression

    Amt_used * LOOKUP("components", "Comp_Num=components->Comp_Num", "Cost_per_unit")
    This may evaluate correctly but does it give you the desired result? Unless I'm missing something the filter expression in your second parameter matches every record in the lookup table.

    Take a minute and tell us what you're doing.

    Take a second minute and tell where you're defining the calc expression.

    Take a third minute and tell us about the table and or set structures that are present.

    Thanks.

    -- tom

    ps. Welcome to the message board!

    Comment


      #3
      Re: LOOKUP within a calculated field expression

      With this expression I have "Amt_Used" which refers to the amount of "Prim_Comp", the primary component used in an operation. These two fields are located in the table "material_usage.dbf" and the expression is being written for a calculated field expression in material_usage named "comp_cost".

      "Comp_Num" refers to a field in the table "components.dbf" that contains unique codes for different operation components. "Cost_per_unit" is a field in this table as well and contains the cost per standard unit of this compound.

      What I'm trying to do is calculate how much it cost to use a certain amount of primary component for an operation.

      Comment


        #4
        Re: LOOKUP within a calculated field expression

        Originally posted by Sperrrow View Post
        With this expression I have "Amt_Used" which refers to the amount of "Prim_Comp", the primary component used in an operation. These two fields are located in the table "material_usage.dbf" and the expression is being written for a calculated field expression in material_usage named "comp_cost".

        "Comp_Num" refers to a field in the table "components.dbf" that contains unique codes for different operation components. "Cost_per_unit" is a field in this table as well and contains the cost per standard unit of this compound.

        What I'm trying to do is calculate how much it cost to use a certain amount of primary component for an operation.
        Amt_used * LOOKUP("components", "Comp_Num=components->Comp_Num", "Cost_per_unit")
        How is the expression based on the Materials_usage table capturing a field value based in the Components table? I think you didn't take that third minute that Tom suggested....
        Take a third minute and tell us about the table and or set structures that are present.
        Mike W
        __________________________
        "I rebel in at least small things to express to the world that I have not completely surrendered"

        Comment


          #5
          Re: LOOKUP within a calculated field expression

          Gotcha,

          Well the tables I'm using here are:

          material_usage(Mt_Number, Op_Code, Prim_Comp, Amt_Used, Op_Comp_1, Op_Comp_2, Prcnt_Scrap, Comp_Cost, Scrap_Cost)

          and

          components(Comp_Num, Component, Supplier, Cost_Per_Unit, Supp_Desc, Mt_Desc)

          I have a set "component_fk" linking material_usage as a child table to the parent table "components" where material_usage(Prim_Comp), material_usage(Op_Comp_1) and material_usage(Op_Comp_2) refer to a value in components(Comp_Num)

          Op_Comp_1 and Op_Comp_2 are non-required character fields for primary component substitutions. The fields that I'm trying to compare are of the same type and length as well.
          Last edited by Sperrrow; 06-23-2010, 10:33 AM.

          Comment


            #6
            Re: LOOKUP within a calculated field expression

            What are the field types of

            material_usage->Prim_Comp

            and

            Components->Comp_Num
            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


              #7
              Re: LOOKUP within a calculated field expression

              material_usage->Prim_Comp and components(Comp_Num) are both character type fields with length 16

              Comment


                #8
                Re: LOOKUP within a calculated field expression

                Amt_used * LOOKUP("components", "Comp_Num='" + Prim_Comp + "'", "Cost_per_unit")


                Amt_used * LOOKUP("table_name", "field_in_lookup_table='" + field in current table + "'", "result_field_in_lookup_table")

                or

                Amt_used * LOOKUP("components", "Comp_Num= " + quote(Prim_Comp), "Cost_per_unit")
                Last edited by Tim Kiebert; 06-23-2010, 10:43 AM.
                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


                  #9
                  Re: LOOKUP within a calculated field expression

                  You make this stuff look easy ^_^

                  Thanks for all the help guys!

                  I scoured the online help about building a filter expression and couldn't find anything even close to this form.

                  Comment


                    #10
                    Re: LOOKUP within a calculated field expression

                    Your welcome

                    Take a fourth minute , ;) and figure out why it works.

                    Here is a link from the help

                    and another from a serial poster ;)
                    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


                      #11
                      Re: LOOKUP within a calculated field expression

                      I had actually looked at both of those resources. The actual help page was confusing because I don't think I was able to define query.filter in a calculated field expression although the form is the same when doing that. I did however use that to aid in the referential integrity issues I had because this is an entirely web-based project. I had been referring to http://www.alphafivewiki.com/Expression+Components for most of the time while trying to figure out this calculation issue.

                      Comment

                      Working...
                      X