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

Ideas for removing blanks in a phone number field

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

  • Ideas for removing blanks in a phone number field

    I am changing a mask in a phone number field and have removed all "(" , ")" , and "-"
    My problem is removing blanks or spaces
    What I am left with is
    "123 1234567" and what I need is "1231234567"
    I have tried an update (search and replace) using "remspecial(phonefield)"
    And I have tried changing field rules to calculated, calculated field set to "remspecial(phonefield)"
    None of the above removes blanks or spaces
    Any thoughts or ideas?
    Thanks
    Tony

  • #2
    Re: Ideas for removing blanks in a phone number field

    Code:
    dim ph as c
    ph = "212 212 7456"
    ?ph
    = "212 212 7456"
    
    ?remspecial(ph)
    = "2122127456"
    looks like it seems to work with remspecial.
    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


    • #3
      Re: Ideas for removing blanks in a phone number field

      Yesterday, I created a sample table and entered a few numbers and I was able to get remspecial to work as well.
      However, when trying it on a 15 year old customer table with 8000 records, it does not
      Just hoping someone else may have encountered something similar and could advise
      But thanks

      Comment


      • #4
        Re: Ideas for removing blanks in a phone number field

        Changing a calculated field calculation expression does not affect existing records. You need to Re-Evaluate Field Rules with the field rule builder open.

        You can also use the function

        A5_RECALC_CALC_FIELDS( Table_Name as C )
        There can be only one.

        Comment


        • #5
          Re: Ideas for removing blanks in a phone number field

          Sorry, I left that out of above post. I did re-evaluate field rules.
          My problem may lie in changing mask, field length, etc over the years.
          I still would like to come up with a solution, because deleting spaces manually will get old.
          Thanks

          Comment


          • #6
            Re: Ideas for removing blanks in a phone number field

            Tony

            Probably time to post an example table with a small amount of data that is OK to expose to the public.

            You may have a hang-over field rule or some other anomaly
            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


            • #7
              Re: Ideas for removing blanks in a phone number field

              I'll try to work on that over the weekend
              Thanks

              Comment


              • #8
                Re: Ideas for removing blanks in a phone number field

                cust_messageboard.zip
                Hopefully this attachment worked
                Thanks

                Comment


                • #9
                  Re: Ideas for removing blanks in a phone number field

                  Another tryAlpha_Message.zip

                  Comment


                  • #10
                    Re: Ideas for removing blanks in a phone number field

                    Originally posted by twwtc View Post
                    [ATTACH]41327[/ATTACH]
                    Hopefully this attachment worked
                    Thanks
                    It worked...

                    Here's an example going back to you to try a couple of things with....

                    1. I used the fieldrule CanSave event to add code to update the fields with remspecial() when a record is saved.

                    Code:
                    'Date Created: 25-Nov-2015 02:54:21 PM
                    'Last Updated: 25-Nov-2015 02:54:21 PM
                    'Created By  : Owner
                    'Updated By  : Owner
                    dim mytbl as P
                    mytbl=table.current()
                    mytbl.BUS_PH1=remspecial(mytbl.Bus_Ph1)
                    mytbl.BUS_PH2=remspecial(mytbl.Bus_Ph2)
                    mytbl.BUS_800=remspecial(mytbl.Bus_800)
                    
                    mytbl.FAX_NUM=remspecial(mytbl.FAX_NUM)
                    
                    mytbl.MOBILE_PH1=remspecial(mytbl.MOBILE_PH1)
                    mytbl.MOBILE_PH2=remspecial(mytbl.MOBILE_PH2)
                    mytbl.MOBILE_PH3=remspecial(mytbl.MOBILE_PH3)
                    
                    mytbl.HOMEPHONE=remspecial(mytbl.HOMEPHONE)
                    mytbl.HOMEPHONE2=remspecial(mytbl.HOMEPHONE2)
                    mytbl.HOMEPHONE3=remspecial(mytbl.HOMEPHONE3)
                    2. I made an operation to update existing records for existing data. Called it UpdPhoneNbrs

                    3. I made a browse (CustAl) with code in the events to use remspecial() on the value so that it is applied when you change the field and leave that field and move to another field on the same line.
                    I did that only on the Phone 1 field so you can see how it differs from the other fields. That code can be cloned and adjusted for each field on the browse if you wish.
                    Then the CanSave event would be unneeded.

                    Note the browse object name is what is used to trigger the <objectname>_onchange event. I modified the phone 1 object name a little bit to make it simplier.

                    events.png
                    It all comes down to where you want the change to happen and appear.

                    Hope it makes sense....

                    cust_messageboard_fromAl.zip
                    Last edited by Al Buchholz; 11-25-2015, 05:48 PM.
                    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: Ideas for removing blanks in a phone number field

                      Thanks Al
                      I will give this a try this weekend and post results
                      Thanks again
                      Tony

                      Comment


                      • #12
                        Re: Ideas for removing blanks in a phone number field

                        For display purposes, the brackets do make a phone number more readable. You could also leave that field as is and add another field without a mask to hold the unformatted data. Use the remspecial there instead.
                        Robin

                        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                        Comment

                        Working...
                        X