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

Field Rules: Table Lookups

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

    Field Rules: Table Lookups

    In my people/contacts (people.dbf) table, I have "firstname" and "lastname" in separate fields. In another table, I have people.type (ptype.dbf). In the field rules for ptype->idperson, I link to people.dbf with the "idperson" field. Now under the source, I list people->idperson, people->lastname, people->firstname. Of course, although the "idperson" number is saved, this displays only the "lastname" in the ptype_>idperson when browsing.

    With all that said, how do I get it to display the first and last name instead of only the last name? What I really want is to concatinate the "firstname"+" "+"lastname" for the display so that "Joe" and "Smith" show as "Joe Smith". Can do on a web page and can do in Access... how do I do it here?

    #2
    Re: Field Rules: Table Lookups

    Number of ways.
    1) Create an on screen Calculated Field with First_name+"[this is a space] "+Last_Name
    2) Create a field in the DB large enough to contain the two data items, make it a calculated field using the above.
    3) If your design is complex, you may need to create a recursive set, but that's a step too far.
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Apologies to anyone I haven't managed to upset yet.
    You are held in a queue and I will get to you soon.

    Comment


      #3
      Re: Field Rules: Table Lookups

      Since the names rarely fill the entire field is generally suggested to use

      trim(First_name)+"[this is a space] "+trim(Last_Name)
      There can be only one.

      Comment


        #4
        Re: Field Rules: Table Lookups

        I stan(d) corrected.
        You could also capitalise the first letter of the name parts to make it look better, and you will have fun with hyphenated names if you do this, as you will with McDonald etc.
        See our Hybrid Option here;
        https://hybridapps.example-software.com/


        Apologies to anyone I haven't managed to upset yet.
        You are held in a queue and I will get to you soon.

        Comment


          #5
          Re: Field Rules: Table Lookups

          Had wanted to avoid adding a field to the table... added unnecessary data space. Wanted something somewhere that would work with coding, or functions or whatever. In the meantime, I did add a field and when the "lastname" and "firstname" are filled code kicks in to add the concatenated name to the "fullname" field which the user will never see. That works but is a clumsy, redundant, "hit it over the head with a hammer" solution.

          By the by, have the solution to the McD's (see Dr. Peter Wayne's "Xbasic for Everyone") but forgot about the hyphenated names. Will have to add that.

          Comment


            #6
            Re: Field Rules: Table Lookups

            Had wanted to avoid adding a field to the table...
            Don't know where you got the impression you needed to add a table field. You can define calculated fields for any layout and place them as if they were table fields.

            Edit: I do see where Ted suggested that. Other comment still stands.
            There can be only one.

            Comment


              #7
              Re: Field Rules: Table Lookups

              As for calculated field, how can one be added for a table field rule's lookup field? I know I can add one to a form but I need it for the lookup. Thus adding the extra field works... just shouldn't need it.

              Comment


                #8
                Re: Field Rules: Table Lookups

                I know I can add one to a form but I need it for the lookup.
                The only reason I can see to add a table field is to store the result. If you don't need to store it, look it up each time you want to display it. A form level calculated field can use a lookup expression.
                There can be only one.

                Comment


                  #9
                  Re: Field Rules: Table Lookups

                  Stan, you are missing the point. In the field rules of a table, under the Lookups tab, if you are using the ptype.dbf (see 1st post), I want to do the list box for the lookup (second section with columns "Source", "Fill" and "Display"), I want to display a full name not just 2 columns for "lastname" and "firstname". This causes the "lastname" to display as the default in a browse or form.

                  Comment


                    #10
                    Re: Field Rules: Table Lookups

                    You can use a mapped table to display the calculated filed in a table lookup
                    Al Buchholz
                    Bookwood Systems, LTD
                    Weekly QReportBuilder Webinars Thursday 1 pm CST

                    Occam's Razor - KISS
                    Normalize till it hurts - De-normalize till it works.
                    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                    When we triage a problem it is much easier to read sample systems than to read a mind.
                    "Make it as simple as possible, but not simpler."
                    Albert Einstein

                    http://www.iadn.com/images/media/iadn_member.png

                    Comment


                      #11
                      Re: Field Rules: Table Lookups

                      Just looked up mapped tables... looks like that is what I need. Mapped tables, huh, just another learning curve. Thanks.

                      Comment


                        #12
                        Re: Field Rules: Table Lookups

                        Have you tried constructing an index using the first and last names?
                        Then a lookup will display whatever you start typing.
                        Also, my favourite, Dynamic Trees!
                        Regarding the hammer solution. If you have so much data that this will cause problems, then I agree. Else, it is a quick and easy way of overcoming coding problems. In a commercial app, the extra data is redundant but greatly simplifies the process. If, for example you need to check for duplicates, you can check one field rather than 2 or possibly 3 if you use a middle name.
                        See our Hybrid Option here;
                        https://hybridapps.example-software.com/


                        Apologies to anyone I haven't managed to upset yet.
                        You are held in a queue and I will get to you soon.

                        Comment


                          #13
                          Re: Field Rules: Table Lookups

                          hello
                          have you tried using mapped tables?
                          it is similar to query in access, using the same data in the table in different perspective.

                          EDIT: this is suggested already, sorry.
                          Last edited by GGandhi; 09-11-2013, 08:00 AM.
                          thanks for reading

                          gandhi

                          version 11 3381 - 4096
                          mysql backend
                          http://www.alphawebprogramming.blogspot.com
                          [email protected]
                          Skype:[email protected]
                          1 914 924 5171

                          Comment

                          Working...
                          X