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() expression in update operation

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

    Lookup() expression in update operation

    The lookup is not getting the correct value in the filter expression, so the returned value is always blank.
    Code:
    a_tbl=table.open("import2")
    update.fields = 1
    update.field1 = "PERSON_ID"
    update.expr1 = "lookup(\"audit_temp\",\"ID=quote(import2->Offense_Id)\",\"person_id\")"
    a_tbl.update()
    In the above code I have prefixed the filter value with table name just to make clear what the source is supposed to be.

    One solution is to use lookupc vs. lookup.
    "lookupc(\"F\",Offense_Id,\"person_id\",\"audit_temp\",\"Cfi\")" works

    But originally the filter was more complex and there was no matching index. So I am still curious if I messed up in the lookup() expression.

    Bill.

    #2
    Re: Lookup() expression in update operation

    Can you try it as

    update.expr1 = "lookup(\"audit_temp\",\"ID=\"+quote(import2->Offense_Id),\"person_id\")"
    There can be only one.

    Comment


      #3
      Re: Lookup() expression in update operation

      Hi Stan,

      That won't work because I want each record in the update to lookup their own offense_id. So the lookup needs to say - take the current offense_id and look it up in audit_temp, then return the person_id. Then do same thing for next record which will have a different offense_id.

      Bill.

      Comment


        #4
        Re: Lookup() expression in update operation

        Works for me. Isn't it essentially the same thing as not quoting the key value in the lookupc()?
        There can be only one.

        Comment


          #5
          Re: Lookup() expression in update operation

          But that is a single value that would apply to every record in the update. Since the update is on import2.dbf, import2->Offense_Id needs to change for each record that is updated.

          Comment


            #6
            Re: Lookup() expression in update operation

            Works for me.

            Try this in AlphaSports.

            Add a "TTL" field to the product table, numeric, 12,2.

            Run this (if the script used one static product_id then you would get the same number in each record in product, it it uses the product_id of the current record you would get a different number)

            Code:
            a_tbl = table.open("product")
            update.fields = 1
            update.field1 = "TTL"
            update.expr1 = "lookup(\"product sales summary\",\"product_id = \"+quote(product_id),\"invoice_items__extension\")"
            a_tbl.update()
            a_tbl.close()
            The update.expr1 gets evaluated for each record, not once at the start of the update.
            Last edited by Stan Mathews; 09-05-2013, 04:31 PM.
            There can be only one.

            Comment


              #7
              Re: Lookup() expression in update operation

              Stan, you have the patience of Job. I failed to catch the diference in your first suggestion (not that it is that hard to see). My brain said there was an extra ", i.e. \"ID=\"', which is how I got onto the static value thing.
              Code:
              'update.expr4 = "lookup(\"audit_temp\",\"ID=quote(import2->Offense_Id)\",\"person_id\")"
              vs.
              update.expr4 = "lookup(\"audit_temp\",\"ID=\"+quote(import2->Offense_Id),\"person_id\")"
              Thanks for sticking with me.

              Bill.

              Comment


                #8
                Re: Lookup() expression in update operation

                That's ok. I was beginning to think I must be misunderstanding the difference between my suggestion and what you actually wanted.
                There can be only one.

                Comment

                Working...
                X