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

Trouble in Calculated Field Land

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

    Trouble in Calculated Field Land

    Hey Everyone..... I'm trying to put together a calculated field on a form that must pull info from another table. The parent table is linked to the child table on a one to one basis with a name field. The parent table contains a field for "Server" (name) and "City". The child table contains a field for "name" (name), a field for "City" and a "Price field. What I am trying to accomplish is for the calculated field to look at the "server" field and "City" field, match those with the corresponding fields in the child table, ("Name" and "City" respectively) and then display the "Price" value from the child field in the calculated field. I'm not sure if I'm having a brain fade or if I'm getting too old for this stuff but I just can't seem to get the appropriate filter expression to achieve this. I thought about a "lookup" function but still can't come up with the appropriate expression.

    Any help would be appreciated. I feel like I'm right on the verge but just can't quite make the leap....lol.

    Thanks for checking out my post.

    Scott

    #2
    Re: Trouble in Calculated Field Land

    It would be sooooo much easier if we had samples of your tables instead of having to build something to demonstrate.
    Given a table named "a" which has the server and city fields and
    a table named "b" which has the name, city, and price fields and the (name) and (city) fields have the same width definition in both.


    A calculated field on a form based on the "a" table where the server field has the objectname "server" and the city field has the object name "city".

    calculated field

    prc = lookup("b","name+city="+s_quote(Server.value+city.value),"price")
    Last edited by Stan Mathews; 07-27-2018, 04:33 PM.
    There can be only one.

    Comment


      #3
      Re: Trouble in Calculated Field Land

      Hey Stan.... Thanks. It doesn't work for me either. I get the same result..... in the expression builder it shows a "C" for a character field and the result is blank. I'm going to see if I can duplicate the 2 tables, rename them and post them here for you to take a look at. Thanks again.......

      Scott

      Comment


        #4
        Re: Trouble in Calculated Field Land

        Tested and works fine here.

        a.zip

        Ignore the addits.dbf in the zip. Accidental inclusion.

        Image 9.png
        There can be only one.

        Comment


          #5
          Re: Trouble in Calculated Field Land

          Ok Stan, here are the 2 tables, "A" and "B". Table "A" is the parent and they are linked one to one by the "Server" field in table "A" and the "Name" field in table "B". There is a "Name" field in table "A" but please ignore that. You will need to put some names in the "Server" field and the "City" field in table "A", and in table "B", you will need to fill some names in the "Name" field, some city names in the "City field with corresponding prices in the "Price" field. Please note that the "Price " field is a character field and not numerical for reasons that we need to sometimes type characters in it also. For example if a server has quit, we will place the word "Quit" in the price field. I need that info to pop up as well.

          Hope this makes sense. Please let me know if you have any other questions. Table "A" was originally started in v4.5 about a hundred years ago....lol. It has been evolving for different purposes ever since then.

          Thanks so much,

          Scott
          Attached Files

          Comment


            #6
            Re: Trouble in Calculated Field Land

            It does work in your example...... not sure why in mine........ huh......

            Scott

            Comment


              #7
              Re: Trouble in Calculated Field Land

              When I try it in my db, it evaluates to a logical as opposed to a character field.

              Scott

              Comment


                #8
                Re: Trouble in Calculated Field Land

                Think I figured it out...different size fields for the linking fields. Will let you know.

                Scott

                Comment


                  #9
                  Re: Trouble in Calculated Field Land

                  I can't do anything with your attachments. Alpha says they have missing memo files, the same name as the tables but with .fpt extensions.

                  You can work around the mismatched field widths with something like

                  prc = lookup("b","alltrim(name)+alltrim(city)="+s_quote(alltrim(Server.value)+alltrim(city.value)),"price")
                  There can be only one.

                  Comment


                    #10
                    Re: Trouble in Calculated Field Land

                    Thanks Stan. No problem. On Friday I changed the field length on one of the tables and that took care of it. Sorry about the tables. My expressions were kind of close but certainly not what was needed. I was unaware that the whole expression could be broken up to form the Filter and Filter Expression. I thought they had to be "complete" unto themselves.

                    Thanks again for your help and patience and letting me pick your brain and something else to file in my notes.

                    Scott

                    Comment

                    Working...
                    X