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

update.fields does not change value via lookup

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

    update.fields does not change value via lookup

    Quick summary of what I am trying to do:

    I have two fields in my database (Script_Num and Script_Name). They are type numeric and character, respectively.

    The database has a lookup set to Script_Num that changes the value of Script_Name depending on what numeric value is stored in Script_Num. For example, if Script_Num = 1, then Script_Name is changed via lookup to be a certain character value.

    That has worked fine until I wrote a script that changed Script_Num from one value to another in batch (that's the code below). It seems that the update expression does to initiate the lookup to change the value of Script_Name based off the new value of Script_Num.

    So in other words, the Script_Num lookup does not run on Script_Name if I batch change the values of Script_Num via update.

    Is this just not how Alpha works or am I missing something here?

    Code:
    this.Disable()
    dim s_num as C	
    
    s_num=topparent:FIELD1.value
    
    tbl=table.open("pricelist")
    
    Query.filter="C_Price>0 .and. Script_num=0"
    Query.order=""
    Query.options="M"
    qry = tbl.query_create()
    
    nrecs = qry.records_get()
    IF (nrecs > 0) then
    	update.fields = 1
    	update.field1 = "Script_num"
    	update.expr1 = s_num
    	'update.expr1 = "'"+reason+"'"
    	tbl.update()
    end if
    qry.drop()
    tbl.close()
    ui_msg_box("Warning",str(nrecs)+" records have been updated!",UI_OK)
    topparent.Close()
    Query.filter=""
    Query.order=""
    Query.options=""
    
    this.Enable()

    #2
    Re: update.fields does not change value via lookup

    A field rule lookup is an aid to manual data entry. You are correct. It does not execute in response to a script/operation.

    You can change your update to include the lookup expression.
    There can be only one.

    Comment


      #3
      Re: update.fields does not change value via lookup

      How would I change my update to include the lookup expression? Thanks!

      Comment


        #4
        Re: update.fields does not change value via lookup

        Not having seen your database, something like...........


        Code:
        IF (nrecs > 0) then
        	update.fields = 2
        	update.field1 = "Script_num"
        	update.expr1 = s_num
        	update.field2 = "Script_name"
        	update.expr2 = [COLOR="#FF0000"]your_lookup_expression[/COLOR]
        	tbl.update()
        end if
        There can be only one.

        Comment


          #5
          Re: update.fields does not change value via lookup

          Sorry for the late response on this. I have not been on site since asking the question.

          As a follow-up, is there any way to force a lookup on an entire table?

          For example:

          I have two tables (address and repairs) and two forms (using the previous tables, respectively). The only field they share is company_name. Both tables have an email field, but the emails are only stored in address's email field. While the other table has the email field, it is a new field and contains no data. I want to match each repairs record (via company_name) to address and populate the email fields.

          Is lookup the best way to do this? If so, how can I run a lookup on an entire table?

          Comment


            #6
            Re: update.fields does not change value via lookup

            A posting operation, probably.
            There can be only one.

            Comment

            Working...
            X