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

Telephone Numbers

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

    Telephone Numbers

    I have a table with a telephone number field in it. Currently, the numbers do not have any dashes in them. The field itself is a character field. Is there a way to run an operation to update the numbers to have dashes in them? ex:
    from 1234567890
    to 123-456-7890

    Thank you,
    Dave

    #2
    RE: Telephone Numbers

    Dave

    Here is a similar question that was posted before.

    http://msgboard.alphasoftware.com/alphaphorum/read.php3?sortby=lastreply&direction=desc&num=11&id=9032&thread=9032
    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


      #3
      RE: Telephone Numbers

      A bigger question here is why store the dashes at all??

      On all of your forms, reports and letters, you can format the numbers in whatever way you would like.

      Tom

      Comment


        #4
        RE: Telephone Numbers

        Dave,

        In the field properties of the field in question, you can set a mask for the telephone number so that the dashes are in the appropriate position AND you can have the field only accept numerics even though it is a character field.

        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


          #5
          RE: Telephone Numbers

          The easiest way to do what you need is to go to the field rules for the table where you have the phone number field.
          Then under tab "Data Entry" look for Mask style and choose Simple. A pop up screen will come up and you can choose a pre-built mask or you can just create yours by typing :
          000-000-0000 on the mask.
          Hope this helps.

          The Mexican
          The Mexican

          Comment


            #6
            RE: Telephone Numbers

            Thank you all for your replies. Here's the thing, There is a mask in the field rules now but there wasn't to begin with. So, I have around 5000 records where the telephone# is without dashes. We do view these records on forms but we also use them for mailings which is why formatting the field on the form itself would not solve my problem.

            Al pointed me to the following calc which I'm trying now.
            left(tel,3) + "-" + substr(tel,4,3) + "-" + substr(tel,7,4)


            Thanks,
            Dave

            Comment


              #7
              RE: Telephone Numbers

              By the way, some numbers are 7 characters long and some are 10. Is there a way to state I only want to run this calc when the length is 7 and run the other calc when the length is 10?

              left(printtel,3) + "-" + substr(printtel,4,3) + "-" + substr(printtel,7,4)

              Thank you,
              Dave

              Comment


                #8
                RE: Telephone Numbers

                I would probably do as "the Mexican" says, except make the mask conditional on the lenght of the data in the field. The mask is used in all forms, reports, labels, etc. and DOESN'T need to be stored in the data itself.
                see attached:

                Tom

                Comment


                  #9
                  RE: Telephone Numbers

                  Dave

                  Since the choice happens when the area code is missing, use alltrim and padl functions to make a string that is either

                  padl(alltrim(phonefield),10," ")
                  to get:

                  ' 5551212'
                  or
                  '6085551212'

                  Then the function should work and give you

                  ( ) 555-1212
                  or
                  (608) 555-1212
                  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


                    #10
                    RE: Telephone Numbers

                    This is what I've got for an operation but it's not quite right. Can you see what's wrong? It works until I add the or condition.

                    if(len(trim(printtel))=10,
                    left(printtel,3) + "-" + substr(printtel,4,3) + "-" + substr(printtel,7,4),"").or. if(len(trim(printtel))=7,
                    left(printtel,3) + "-" + substr(printtel,4,3),"")

                    Comment


                      #11
                      RE: Telephone Numbers

                      Thomas

                      It requires less storage to not store the mask in the data. The disadvantage is that an export operation outputs the unmasked data. If the mask is stored, the exported data contains the mask.

                      All you can do is give the client the options and let them decide.
                      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


                        #12
                        RE: Telephone Numbers

                        Replace the .or. with a comma.

                        Read the syntax as "else" instead of "or"
                        Gary S. Traub, Ph.D.

                        Comment


                          #13
                          RE: Telephone Numbers

                          The dashes also create problems when doing searches. If the dash is included in the data, the user needs to include the dash when searching and vice versa.

                          To solve the issue in one of my apps, I created a function called Phone_dash() that adds dashes to create a format such as either:
                          123-4567
                          or
                          123-456-7890

                          By using this in the CanWrite event, the phone number is ALWAYS formatted correctly regardless of parenthesis, spaces, or a leading "1" that the user might try to input.

                          I then use 'scripted finds' in this application for phone number searches. The user is prompted for a phone number using ui_get_text() and the number is converted in the script. Something like this:

                          phone_in = ui_get_text("ENTER PHONE","Enter....")
                          phone_in = phone_dash( phone_in )
                          parentform.find(phone_in)

                          The function can also be used in a global update to convert existing numbers.

                          Here's the function for you to cut-and-paste. (The method I'm using to retain the indents may cause double line spaces. If so, I assume you can find a way to remove them!)

                          [code]
                          FUNCTION Phone_dash AS C (Phone_in AS C )
                          'Description:Adds dashes to phone numbers as necessary and removes leading "1"s. Assumes 333-444-1234 output format will always be valid.
                          DIM phone_w as C
                          phone_w = remspecial(phone_in) 'Define the 'working' number.

                          IF phone_w = ""
                          Phone_dash = phone_w
                          EXIT FUNCTION
                          END IF

                          'Remove any leading 1 that might be for long distance.
                          'Left the ability to start an area code or exchange with "1" because of a
                          ' conversion routine I use to "encrypt" phone numbers. (Although, it would be
                          ' better to change the "encryption" too so all beginning 1s becomes 2s...)
                          IF left(phone_w,1)="1" .and. len(phone_w)=11
                          phone_w = substr(phone_w,2)
                          END IF

                          phone_w = stuff( phone_w, 4, 0, "-" )
                          IF len(trim(phone_w))>8
                          phone_w = stuff( phone_w, 8, 0, "-" )
                          END IF

                          Phone_dash = phone_w

                          END FUNCTION

                          Comment


                            #14
                            RE: Telephone Numbers

                            Sorry, I forgot there was a long line in the function that would force the wide message.

                            Comment


                              #15
                              RE: Telephone Numbers

                              Cal,
                              This is quite brilliant and if you read your comments closely one will learn a tremendous amount. Thanks for taking the time to comment.

                              Comment

                              Working...
                              X