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

Lookupc() function "stuck"

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

    Lookupc() function "stuck"

    I have 2 tables, TableA and TableB. I made the field 'B_maxisnumber" in TableB a calculated field with the following expression:

    Lookupc("C","B_maxisnumber","A_maxisnumber","t_tableA","maxis_numb")

    A_maxisnumber is the corresponding field in TableA and maxis_numb is an index in each table for the B_maxisnumber and A_maxisnumber fields.

    In the expression builder, it shows the first record but as I scroll through the records, the value doesn't change, it remains constant.

    What am I missing?

    Thanks,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    Re: Lookupc() function "stuck"

    Ken,

    Are the fields the exact same size and layout? Is the index expression the same? If not, try padr() or padl() to make the fields match.

    One other thought is that the expression may just be fine, but because it is a calculated field, you might just need to recalc the calculated fields. Right click on the table and under Utilities, there is the recalc option.

    Hope this helps,

    Tom

    Comment


      #3
      Re: Lookupc() function "stuck"

      Nice work Kenn.. you explained it very well to those who never understood before what a catch 22 is!

      You are looking up the closest match to the value in a field, but that field's value is a calculated one derived from the lookup value!

      Very cute!

      Did we miss our coffee this morning? Or did Obama forget to bail out caffeine?

      Comment


        #4
        Re: Lookupc() function "stuck"

        He's right,

        You are trying to use a field as the key of a lookup to fill itself.

        You would need some other field common to both tables so that you can get maxisnumber from tableA to TableB.

        Comment


          #5
          Re: Lookupc() function "stuck"

          Hi Kenn,

          Originally posted by forskare View Post
          I have 2 tables, TableA and TableB. I made the field 'B_maxisnumber" in TableB a calculated field with the following expression:

          Lookupc("C","B_maxisnumber","A_maxisnumber","t_tableA","maxis_numb")

          A_maxisnumber is the corresponding field in TableA and maxis_numb is an index in each table for the B_maxisnumber and A_maxisnumber fields.

          In the expression builder, it shows the first record but as I scroll through the records, the value doesn't change, it remains constant.

          What am I missing?
          Lookupc("C",some_value,"A_maxisnumber","t_tableA","maxis_numb")


          You are looking at the 1st record in table "t_tableA" (you also called it just "tableA", so I assume that was a typo) whose index's key value in index named "maxis_numb" is greater than or equal to some_value and returning a value of expression A_maxisnumber, which better evaluate to a character value (since you are using lookupc() ) The key value of some_value should be the same type as the index's expression, typically type C, N or D

          But it needs to be a value from something, not the fieldname you want the value stuffed into.
          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


            #6
            Re: Lookupc() function "stuck"

            Hi Tom,

            Everything is the same except for the field names, A & B and the table names.

            Yo, Gabe,

            No, I didn't miss it but since I dislike coffee, I had a Mountain Dew.

            I thought the function of this function is to get the value in A_maxisnumber in tableA and fill field B_maxisnumber in tableB with the value.

            Shouldn't the explanation of the Lookupc() function in A5 Help mention this?

            Thanks,

            kenn
            TYVM :) kenn

            Knowing what you can achieve will not become reality until you imagine and explore.

            Comment


              #7
              Re: Lookupc() function "stuck"

              Hi Kenn,

              Originally posted by forskare View Post
              I thought the function of this function is to get the value in A_maxisnumber in tableA and fill field B_maxisnumber in tableB with the value.
              But which record do you want in tableA? There has got to be a way (normally a value) to lookup in the index a specific record. You haven't specified a value to get to a specific record!
              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


                #8
                Re: Lookupc() function "stuck"

                Originally posted by csda1 View Post
                Lookupc("C",some_value,"A_maxisnumber","t_tableA","maxis_numb")

                You are looking at the 1st record in table "t_tableA" (you also called it just "tableA", so I assume that was a typo) whose index's key value in index named "maxis_numb" is greater than or equal to some_value and returning a value of expression A_maxisnumber, which better evaluate to a character value (since you are using lookupc() ) The key value of some_value should be the same type as the index's expression, typically type C, N or D

                But it needs to be a value from something, not the fieldname you want the value stuffed into.
                Hi Ira,

                You made your post while I was typing my last response and I needed to do other things so just now getting back.

                I called the tables A & B for the purpose of trying to make my explanation easier. This is the actual expression:

                LOOKUPC("C","A_Maxisnumber","A_Maxisnumber","t_clients","Maxis_Numb")

                The fields in both tables now the same name, A_Maxisnumber.

                kenn
                TYVM :) kenn

                Knowing what you can achieve will not become reality until you imagine and explore.

                Comment


                  #9
                  Re: Lookupc() function "stuck"

                  Ken,

                  Just so I understand. You are trying to fill field "A_maxisnumber" in table B with the value of "A_maxisnumber" from Table A, right?

                  If so, in table B, before the lookup, "A_maxisnumber" is empty until filled. Your lookup is attempting to use this field to lookup into table A. As there is no value in this field to beginwith, it can't find anything in table A. You would need to use some different field common to both tables as the lookup key in order to fill the field "A_maxisnumber".

                  Tom

                  Comment


                    #10
                    Re: Lookupc() function "stuck"

                    Oh My, Oh My, Oh Oh

                    I think I found the problem. Some how, the value of the maxisnumber field in TableA changed to the value of this field in the first record so now, all records have the same value. Good thing I have backups.

                    kenn
                    TYVM :) kenn

                    Knowing what you can achieve will not become reality until you imagine and explore.

                    Comment


                      #11
                      Re: Lookupc() function "stuck"

                      Ken, be very careful here...

                      Ihave 2 tables, TableA and TableB. I made the field 'B_maxisnumber" in TableB a calculated field with the following expression:

                      Lookupc("C","B_maxisnumber","A_maxisnumber","t_tableA","maxis_numb")
                      You're using a field - "B_maxisnumber" as a key into tableA to fill itself. If B_maxisnumber is blank to start with, then the closest match will be the lowest value of "A_maxisnumber" in tableA for ALL records where "B_maxisnumber" is initially blank.

                      Tom

                      Comment


                        #12
                        Re: Lookupc() function "stuck"

                        Originally posted by Tom Henkel View Post
                        Ken,

                        Just so I understand. You are trying to fill field "A_maxisnumber" in table B with the value of "A_maxisnumber" from Table A, right?

                        If so, in table B, before the lookup, "A_maxisnumber" is empty until filled. Your lookup is attempting to use this field to lookup into table A. As there is no value in this field to beginwith, it can't find anything in table A. You would need to use some different field common to both tables as the lookup key in order to fill the field "A_maxisnumber".

                        Tom
                        Hi Tom,

                        You are correct in your assessment but my understanding is not the same as yours. This is what I understand:

                        Key value = the value in the A_maxisnumber field of TableA. To get this value, one must use the field name which contains the sought after value.
                        Lookup Expression = The field in TableA which contains the value which is A_maxisnumber.
                        Lookup Table = The table which contains the field (A_maxisnumber) which contains the value to be obtained.
                        Index = The index in the Lookup Table, TableA, which is based on the field, A_maxisnumber. The same index exists in TableB for the common field, A_maxisnumber.

                        Since this expression is in the field rules for the field A_maxisnumber in TableB, it should 'get' and 'set' the value. The common linking field is a_maxisnumber. Is it possible one cannot do this with the common field itself?

                        Thanks,

                        kenn
                        TYVM :) kenn

                        Knowing what you can achieve will not become reality until you imagine and explore.

                        Comment


                          #13
                          Re: Lookupc() function "stuck"

                          Since this expression is in the field rules for the field A_maxisnumber in TableB, it should 'get' and 'set' the value. The common linking field is a_maxisnumber. Is it possible one cannot do this with the common field itself?
                          what value from table B will it use to retrieve the field from tableA if the field is initially blank?

                          Tom

                          Comment


                            #14
                            Re: Lookupc() function "stuck"

                            Originally posted by Tom Henkel View Post
                            what value from table B will it use to retrieve the field from tableA if the field is initially blank?

                            Tom
                            What I don't understand is why it is going to retrieve a value from tableB if tableB is not part of the expression. Does the expression not say to look in tableA?

                            kenn
                            TYVM :) kenn

                            Knowing what you can achieve will not become reality until you imagine and explore.

                            Comment


                              #15
                              Re: Lookupc() function "stuck"

                              you're telling it to use the value of the field "B_maxisnumber" from table B to lookup into table A.

                              Comment

                              Working...
                              X