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

what expression to concatenate and capitalize?

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

    what expression to concatenate and capitalize?

    Working on a report but would also apply for a form.
    I know I can concatenate (and remove unused spaces) my last name and first name fields by using the expression + and alltrim. I was also interested in making sure that those names were capitalized (first letter only).
    The expression I used to concatenate (and add a space) is:
    alltrim(Fname) + " " alltrim(Lname)
    If I want to make sure that the first letter of the Fname and Lname fields were capitalized would I use the W_upper expression or F_upper and where would I put it in the expression? Would it be something like this (which works) or is there something better?
    F_upper (alltrim(Fname)) + " " F_upper (alltrim(Lname))

    #2
    Re: what expression to concatenate and capitalize?

    Hi doug,
    F_upper (alltrim(Fname)) + " " + F_upper (alltrim(Lname))
    just needs a "+" (typo I assume)----use what works and see nothing wrong with the simple being used!
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


      #3
      Re: what expression to concatenate and capitalize?

      mike,
      thanks for your reply. The lack of the + was a typo in the post.
      However, I found that in order to get it to work my expression is:
      F_upper(NW_Lower(alltrim(Fname))) + " " + F_upper(NW_Lower(alltrim (Lname)))
      Explanation: the F_upper capitalizes the first letter of the character string; the NW_Lower changes all the letters of the string except the 1st letter to lowercase.
      This is necessary for:
      1: the scenario where the person entering the data makes it all lower case (charlie brown)
      2: the scenario where the person entering the data makes it all upper case (CHARLIE BROWN)
      This also works for cHarlie BrOwN, etc.
      By the way, is there any way to prevent a person entering data in caps, etc. I would like it so that I don't find that a report looks strange because alot of data is entered in caps.
      Thanks again
      Last edited by dlazenby; 11-01-2009, 11:11 PM. Reason: typo

      Comment


        #4
        Re: what expression to concatenate and capitalize?

        doug,
        If this is something you want to have always on any layout based on a specific table, then maybe the use of Field Rules (Transformation tab) for the table used would be the easiest way.
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #5
          Re: what expression to concatenate and capitalize?

          Doug,

          I agree with Mike that it would be better to control the cases at the table level. The reason I say this is that there are many exceptions to the general rules. What about lastnames of "DeLuca", "Miller-Smith", and "McCormick". Do you want these to show up as "Deluca", "Miller-smith", and "Mccormick" on the report? Also, if you do not have a "suffix" field, then a lastname of "Phillips III" would show up as "Phillips iii".

          When these people are first entered into the system, if the user controls the letter cases to be what the people prefer, you can rely on these entries from that point forward.

          Steve

          Comment


            #6
            Re: what expression to concatenate and capitalize?

            Mentioning the exceptions brings to mind a few threads regarding this from the past....the Code Archive has something you may also want to consider from Cal Locklin.

            http://msgboard.alphasoftware.com/al...ght=capitalize
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment


              #7
              Re: what expression to concatenate and capitalize?

              Excellent responses. I did not think of those issues. I am not familiar with the transformation expressions so I will have to delve into that.
              I will look into that archive post also.
              Thanks again very much!

              Comment


                #8
                Re: what expression to concatenate and capitalize?

                The only really safe formatting for names is Upper (convert entire name to upper case) or Lower (convert entire name to lower case) All other options will, with any given name will become problematic.

                If you are going to use one of the formatting options, it is a lot cleaner to do it using the Field Rules Transformations option.

                Dave
                Dave Jampole
                www.customalpha.com

                Women and cats will do whatever they want. The sooner men and dogs realize that, the happier they will be.

                Comment


                  #9
                  Re: what expression to concatenate and capitalize?

                  I agree with Mike that it would be better to control the cases at the table level. The reason I say this is that there are many exceptions to the general rules. What about lastnames of "DeLuca", "Miller-Smith", and "McCormick". Do you want these to show up as "Deluca", "Miller-smith", and "Mccormick" on the report? Also, if you do not have a "suffix" field, then a lastname of "Phillips III" would show up as "Phillips iii".
                  miller-smith will come out Miller-Smith when done with the field rules transformation. Been doing this for a long time

                  phillips iii will come out Phillips Iii unless the user inputs phillips III and then it will comeout Phillips III.

                  Inputting deluca will come out Deluca unless the User changes the "l" to "L" and then it will come out as DeLuca.

                  Once saved in the dbf field that way, it will not change unless you mess with it someway.


                  .
                  Dave Mason
                  [email protected]
                  Skype is dave.mason46

                  Comment

                  Working...
                  X