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



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

Default based on current record

  • Filter
  • Time
  • Show
Clear All
new posts

  • Default based on current record

    I'm sure this has been covered, but I can't find it. I'd like to lookup a value in another table using the lookup or lookupc expressions and insert that value in the current record so the operator can view the value of the lookup. Using the default field rule, how can I get the looked up value to show on the form and how can I use the values being input to the form in the lookup expression. I'm trying to lookup a value based on the area code and exchange. I've tried placing the expression in the on depart event of the telephone number field on the form to no avail.

  • #2
    RE: Default based on current record

    Hi Ohlen,

    I'm not sure I get it. You are writing lookup code to a form or field on_depart or other event? But why would you not simply use the lookup function to define a simple default expression in field rules?

    Or am I missing something?

    Bill Hanigsberg


    • #3
      RE: Default based on current record

      Hello Ohlen,

      If I'm understanding you, just put a calculated field on the form and create the expression using the lookup() function. Now you can reference this field, but not of course in the field rules as it exists only when the form exists.

      Good luck,


      • #4
        RE: Default based on current record

        Bill and Jim,
        Thanks for the reply. I guess I wasn't entirely clear. What I want to do is lookup a field in a table based on the combination of telephone area code and telephone exchange while information is being typed into the form. The looked up table is indexed on a 6 character field in which the first 3 characters are the area code and the second 3 the exchange. So far so good. The operator inputs the telephone number as (xxx) xxx-xxxx and I extract the 6 characters using the substr(telno,2,3)+substr(telno,6,3). I tried the lookup expression in the default field but it didn't work. I think because the record is not yet saved it couldn't get find telno in the table. Then I tried it on the on depart event of the telno field using object addressing like this resultfield.text substr(telno.text,2,3)+substr(telno.text,6,3) and could not get the result field to update. Hope this makes a little more sense.


        • #5
          RE: Default based on current record

          Hi again,

          I think I have it now--what you're attempting, that is.

          As I see it there are two parts to test separately:

          -does the lookup work
          I assume you have verified that the lookup syntax actually functions. I would write the result of the lookup to the trace window in hopes of verifying that the lookup works and works from the event to which I have attached the code.

          -does the field update
          Well, you've said it doesn't. What is the syntax you are using. Are you writing to the field's value or text property? Have you refreshed the form's field object?

          Bill Hanigsberg


          • #6
            RE: Default based on current record

            Thanks for the reply

            >>I assume you have verified that the lookup syntax actually functions. I would write the result of the lookup to the trace window in hopes of verifying that the lookup works and works from the event to which I have attached the code.>does the field update
            Well, you've said it doesn't. What is the syntax you are using. Are you writing to the field's value or text property? Have you refreshed the form's field object?


            • #7
              RE: Default based on current record

              Here is the expression I'm using in the on depart of the telno field.

              Referred_To.value=lookup("tel exchanges.dbf","areaexch=substr(this.text,2,3)+substr(this.text,7,3)","referred_to")

              The substr expressions evaluate properly and will fill in the trace window as expected. The lookup functions and will fill in the trace window as expected if the substr expressions are replaced with a character string. The problem seems to be in using the substr expressions as part of the lookup. Any suggestions.


              • #8
                RE: Default based on current record

                Here's what I finally got to work. Can anyone tell me why it works when I make an intermediate variable but won't work when evaluating the substr expressions as a part of the lookup.

                This works:
                Referred_To.value=lookup("tel exchanges.dbf","areaexch='"+codeexch+"'","referred_to")

                This doesn't:
                Referred_To.value=lookup("tel exchanges.dbf","areaexch=substr(this.text,2,3)+substr(this.text,7,3)","referred_to")


                • #9
                  RE: Default based on current record


                  It may be that in the case where you used a variable, you explicitly enclosed it in single quotes, but in the case of the substring functions, you did not??



                  • #10
                    RE: Default based on current record


                    I also got this to work. Seems you have to force the evaluatin of the expression which works with the plus signs or by using a variable. Thanks to all who prodded me along on this.

                    This works:
                    Referred_To.value=lookup("tel changes.dbf","areaexch='"+codeexch+"'","referred_to")

                    This doesn't:
                    Referred_To.value=lookup("tel exchanges.dbf","areaexch=substr(this.text,2,3)+substr(this.text,7,3)","referred_to")

                    And now this works:
                    Referred_To.value=lookup("tel exchanges.dbf","areaexch='"+substr(this.text,2,3)+substr(this.text,7,3)+"'","referred_to")