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

restrict character input

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

  • restrict character input

    Is it possible to dis-allow a specific character to be entered while allowing all other characters?

    I don't care if it ignores the keypress or indicates that the character is not allow via a warning popup or??.

    Thanks.

  • #2
    RE: restrict character input

    I'm not sure if a field rule mask will work, it might. Otherwise use the OnKey event.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


    • #3
      RE: restrict character input

      The only issue with the OnKey event is that it applies to the whole form. If the restriction only applies to one field, you would probably have to write a script for the CanWrite field event. Something like this should work if you don't want the user to type the letter "L" or "l":

      IF atc( "L", a_field_value ) > 0
      ui_msg_box( "*** ERROR ***", "Can't do that...retype it." )
      cancel()
      END

      Comment


      • #4
        RE: restrict character input

        Cal,

        You are correct that the OnKey event applies to the whole form (as does the OnTimer event), but that can easily circumvented. It is very easy to change the event code dynamically. In fact, both of these events should be done this way, as they both have very high overhead on system performance when not a null value.

        In the OnArrive for the field, I would put code similar to

        dim shared OnKey_orgcode as C
        OnKey_orgcode=parentform.event.OnKey
        parentform.event.OnKey="new code here as an expression"



        In the OnDepart for the field, the code would look like this,

        dim shared OnKey_orgcode as C
        parentform.event.OnKey=OnKey_orgcode


        Some people try to put a ton of code in the new code expression(which creates headaches trying to account for quotes, double quotes etc), however, I prefer to keep it simple, like 1 of the 2 below

        parentform.event.OnKey="OnKey_newcode_function_name()"

        or

        parentform.event.OnKey="script_play('OnKey_newcode_scipt_name')"

        Regards,

        Ira J. Perlow
        Computer Systems Design & Associates
        [email protected]
        Regards,

        Ira J. Perlow
        Computer Systems Design


        CSDA A5 Products
        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
        CSDA Barcode Functions

        CSDA Code Utility
        CSDA Screen Capture


        Comment


        • #5
          RE: restrict character input

          Cal:

          With an OnKey event for a single field, you can help things along with a

          if this.active()=field_to_test then
          'code here
          else
          end
          end if

          helps keep the overhead down.

          Finian
          Finian

          Comment


          • #6
            RE: restrict character input

            Finian

            While qualifing the code with what field is active will help, I think it's effect is trivial. I believe the major amount of overhead is whether the ONKEY event is active or not (in other words the code is set to null or not). Proof of this would be seen in the responsiveness of the keystrokes.

            Regards,

            Ira J. Perlow
            Computer Systems Design & Associates
            [email protected]
            Regards,

            Ira J. Perlow
            Computer Systems Design


            CSDA A5 Products
            New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
            CSDA Barcode Functions

            CSDA Code Utility
            CSDA Screen Capture


            Comment


            • #7
              RE: restrict character input

              Ira,
              your idea is fascinating, but I can barely grasp it. could you write a short script of some simple practical use.
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              [email protected]

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment

              Working...
              X