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

Phone Number mask problems

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

  • Phone Number mask problems

    I have a character field for the customers phone number. It uses the Phone(US/Canada) mask.

    The problem is users are entering () - and spaces which screws up the phone number displaying right on invoices and such.

    Once they do that it seems impossible to clear the trash out even when re-entering the phone number.

    Is there anyway to stop them from being able to do anything but enter the number 0-9 ?

    Also I have the "Do not store mask literals in filed" checked

    Or do I just have to turn off the mask.

  • #2
    Re: Phone Number mask problems

    Many ways, an easy one:
    In the OnDepart event of the field object/control, use this script:
    Code:
    tel_fld=remspecial(tel_fld)

    Comment


    • #3
      Re: Phone Number mask problems

      Is there anyway to stop them from being able to do anything but enter the number 0-9 ?
      I just tested in a dummy table, when you have a mask -Phone(US/Canada), it seems to be the default behavior. tested in default browse and default form only.
      I was not able to enter anything but 0-9 and when actually enter "(", ")", "-" I takes them if they are supposed to be there if not it is not taken.
      may be that there is something more to it than the posted material.
      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


      • #4
        Re: Phone Number mask problems

        Originally posted by G Gabriel View Post
        Many ways, an easy one:
        In the OnDepart event of the field object/control, use this script:
        Code:
        tel_fld=remspecial(tel_fld)
        Would not work using the field (object) name from the form. It required a variable. Had to modify it.

        Code:
        dim phone2 as c
        phone2 = parentform.phone
        parentform:phone.value=remspecial(phone2)

        Comment


        • #5
          Re: Phone Number mask problems

          Originally posted by GGandhi View Post
          I just tested in a dummy table, when you have a mask -Phone(US/Canada), it seems to be the default behavior. tested in default browse and default form only.
          I was not able to enter anything but 0-9 and when actually enter "(", ")", "-" I takes them if they are supposed to be there if not it is not taken.
          may be that there is something more to it than the posted material.
          Same with me but some how some of them can figure out how to screw it up.

          It shows fine on the forms even if they use those symbols where allowed. It is when it is displayed on a report using,
          Code:
          MASK(PHONE,"( )| ...
          in the rich text that it sometime rears its head.

          Comment


          • #6
            Re: Phone Number mask problems

            Originally posted by preston2 View Post
            Would not work using the field (object) name from the form. It required a variable. Had to modify it.

            Code:
            dim phone2 as c
            phone2 = parentform.phone
            parentform:phone.value=remspecial(phone2)
            That is the field object's name!
            No need for variable.
            You could also reference the field's name but you have to preface it with the table name.

            Comment


            • #7
              Re: Phone Number mask problems

              Originally posted by G Gabriel View Post
              That is the field object's name!
              No need for variable.
              You could also reference the field's name but you have to preface it with the table name.
              I did not try it prefacing the field with the table name but the other ways I tried kept getting "variable not found" error messages so I created a variable.

              Comment


              • #8
                Re: Phone Number mask problems

                I didn't know if you were doing this from a form, an xdlg or something else. When I put tel_fld, I thought you will understand to use the proper field name in whichever context you are doing that.

                Comment


                • #9
                  Re: Phone Number mask problems

                  Originally posted by G Gabriel View Post
                  When I put tel_fld, I thought you will understand to use the proper field name in whichever context you are doing that.
                  I guess not. I put fields on a form, they also have object names so to me just saying tel_fld means the field anyway you need to access it.
                  Stating "In the OnDepart event of the field object/control" also lead me to believe you where talking about the field on the form and not directly referring the field in the table. Besides a user would never edit a table field directly so to me that meant the field/object on the form.

                  table->tel_fld would have left no doubt that you a referring to the field in a table and not the field on a form.

                  Just a slight misunderstanding but that is ok because it works either way.

                  Comment

                  Working...
                  X