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

Mask/Transformation

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

  • Mask/Transformation

    I would like to apply a rule to a field that would allow only upper case letters and space, expl: JOHN HAWTHORN AT ALPHA FIVE
    If I use mask with a series of Ls I get the upper case letters but can't enter space between words.
    If I use transformation I can turn the data to upper case and use space but A5 allows any character.
    Any suggestion? Thanks

  • #2
    Re: Mask/Transformation

    Gaby,
    IOW, you want to limit entries to only letters and spaces----no numbers, dashes, slashes, commas,....any other special characters. Right?
    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: Mask/Transformation

      Gaby,
      Even though the ampersand (&) is supposed to only allow character values (my understanding), it does allow numeric as well... :( But use this anyway as it does allow spaces.

      So one work-around on a form would be:
      OnKey event
      Code:
      dim shared flag_cancel as L
      flag_cancel=.F.
      select
      case a_user.key.value = "0" 
      a_user.key.handled = .T. 
       flag_cancel=.T.
      case a_user.key.value = "1" 
      a_user.key.handled = .T.
       flag_cancel=.T.
      case a_user.key.value = "2" 
      a_user.key.handled = .T.
       flag_cancel=.T.
      case a_user.key.value = "3" 
      a_user.key.handled = .T.
       flag_cancel=.T.
      case a_user.key.value = "4" 
      a_user.key.handled = .T.
       flag_cancel=.T.
      case a_user.key.value = "5" 
      a_user.key.handled = .T.
       flag_cancel=.T.
      case a_user.key.value = "6" 
      a_user.key.handled = .T.
       flag_cancel=.T.
      case a_user.key.value = "7" 
      a_user.key.handled = .T. 
       flag_cancel=.T.
      case a_user.key.value = "8" 
      a_user.key.handled = .T. 
       flag_cancel=.T.
      case a_user.key.value = "9" 
      a_user.key.handled = .T.
       flag_cancel=.T.
      end select
      CanSave event
      Code:
      if  flag_cancel=.T.
          cancel()
      end if
      More can be added as well for other unwanted characters---possibly remspecial() could be used somewhere as well on the field....
      Probably ways to condense the code but think more users can see what is happening when it is a bit more verbose.
      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


      • #4
        Re: Mask/Transformation

        Hello Mike:
        I though of the Onkey as a possible solution, but has 2 issues: 1) Other fields on the form will have the same restrictions; 2) I have to include all other characters like , . ; / + _ - ) ( etc...
        It's more complicated than it is worth, I think I'll leave at that.
        I saved your code in my notes for future reference. Thanks

        Comment


        • #5
          Re: Mask/Transformation

          Gaby,
          I know...you said to leave it alone! I couldn't.

          Issue #1 solved fairly easy (tried is_object() with no success) by using a logical variable, setting it in the OnInit of the form, the OnArrive and OnDepart events of the field. May be a way for the special characters but not currently....
          Code:
          '==========OnInit form event  Up_Mask is the name of the field.
          dim shared UpMask_flag as L
          UpMask_flag=.F.
          
          '=========Up_Mask field OnArrive event
          UpMask_flag=.T.
          
          'Up_Mask field OnDepart event
          UpMask_flag=.F.
          
          '=======OnKey
          dim shared flag_cancel as L
          flag_cancel=.F.
          
          if UpMask_flag
          
            select
            case a_user.key.value = "0" 
              a_user.key.handled = .T. 
              flag_cancel=.T.
            case a_user.key.value = "1" 
              a_user.key.handled = .T.
              flag_cancel=.T.
            case a_user.key.value = "2" 
              a_user.key.handled = .T.
              flag_cancel=.T.
            case a_user.key.value = "3" 
              a_user.key.handled = .T.
              flag_cancel=.T.
            case a_user.key.value = "4" 
              a_user.key.handled = .T.
              flag_cancel=.T.
            case a_user.key.value = "5" 
              a_user.key.handled = .T.
              flag_cancel=.T.
            case a_user.key.value = "6" 
              a_user.key.handled = .T.
              flag_cancel=.T.
            case a_user.key.value = "7" 
              a_user.key.handled = .T. 
              flag_cancel=.T.
            case a_user.key.value = "8" 
              a_user.key.handled = .T. 
              flag_cancel=.T.
            case a_user.key.value = "9" 
              a_user.key.handled = .T.
              flag_cancel=.T.
            end select
          
          end if
          '==========CanSave form event
          if  flag_cancel=.T.
              cancel()
          end if
          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


          • #6
            Re: Mask/Transformation

            Thanks Mike.
            While experimenting with your code, I replaced the Select...Case... End Select with:
            Code:
            IF Between(a_user.key.value,"0", "9") Then
             a_user.key.handled = .T. 
             flag_cancel=.T.
            End IF
            seems to work

            Comment


            • #7
              Re: Mask/Transformation

              Exactly!! I bet doing the same with certain chr() s would take care of a bunch of special characters as well.
              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


              • #8
                Re: Mask/Transformation

                As you guessed it, Between(a_user.key.value,"!", "/") did take care of a bunch of characters and left out others. Not knowing the sequence, it's a trial and error process. I'll come back to it when time allows.

                Comment


                • #9
                  Re: Mask/Transformation

                  I was thinking more along the lines of the following:
                  Code:
                  if between(asc(a_user.key.value),0,31).or. between(asc(a_user.key.value),33,64).or. between(asc(a_user.key.value),91,96).or. asc(a_user.key.value)>=123
                    a_user.key.handled = .T. 
                    flag_cancel=.T.
                  end if
                  Although chr(32), which is a space, for some reason is still included....as you said---something to fool around with later!
                  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

                  Working...
                  X