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

restricting characters entered in text box

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

  • restricting characters entered in text box

    i have a text-box on a form for license plate. license plates have no letter "o", just number "0". i want to correct the user's entry if necessary when they depart the field, but can't figure out how....

    the file is "tickets". the data entry form is "ticket_entry_w_browse". the field name and the form object name are both "REGISTRATION".

    i've tried using stritran(":ticket_entry_w_browse.registration.value","o","0") and other variants of stritran in "can depart" and "on depart", but think i'm missing something simple because they don't work...

    if there's no easy way, i'll just run an operation after they close the "ticket_entry_w_browse" and return to the menu.

  • #2
    Re: restricting characters entered in text box

    Try
    Code:
    this.text = stritran(this.text,"o","0")
    Tim Kiebert
    Eagle Creek Citrus
    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

    Comment


    • #3
      Re: restricting characters entered in text box

      Or

      stritran(:ticket_entry_w_browse.registration.value,"o","0")

      first parameter not quoted.

      Your expression replaces o in the text

      ":ticket_entry_w_browse.registration.value"

      with 0

      Code:
      ? stritran(":ticket_entry_w_browse.registration.value","o","0") 
      = ":ticket_entry_w_br0wse.registrati0n.value"
      There can be only one.

      Comment


      • #4
        Re: restricting characters entered in text box

        thanks to both of you. tim hit the one i finally found after another 2 hours, but still before the message cleared the moderator...

        alpha 4 was sure easier..... but then again i've got 10 years 'programming' it..

        Comment


        • #5
          Re: restricting characters entered in text box

          Jack,

          If you want to capture the data entry error as soon as the error is made, you could try the following:

          Use the onkey() function while your text box has focus to to fire a send_key() command when it sees the o character typed.

          I haven't tried this, but in theory, it should work.

          Louis

          Comment


          • #6
            Re: restricting characters entered in text box

            louis, i like the way your mind works!

            Comment


            • #7
              Re: restricting characters entered in text box

              Louis

              Great idea.

              Jack

              Be sure to find some examples of onkey to base your effort on.

              Ira has some examples that he's posted here and there - along with others...

              It's not the deep end of the pool, but it is a little wavy now and then.

              OnKey can tell what field you are in and the appropriate coding is needed to change values only in the field(s) that you desire..
              Last edited by Al Buchholz; 04-30-2010, 04:37 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


              • #8
                Re: restricting characters entered in text box

                The OnKey is a good idea assuming the form has only one field.
                Does it?
                Don't think so.
                If you try to enter: John , you will end up with J0hn.

                I knew someone named J0hn. He was not very popular in school.

                So to modify this a little bit, you need to trigger the onKey event only for this field. How?
                In the onActivate/onDepart events of this field toggle the OnKey event on and off or use stritran() in the OnDepart event.

                What about I & l (small letter L) entered in place of 1 or 5 in place of S? Is that a consideration too?

                If so, a UDF is in order.

                P.S.
                In case I didn't mention it before, I really hate the OnTimer event, the Onley, send_keys() and few others.

                Comment


                • #9
                  Re: restricting characters entered in text box

                  i'm using this:

                  parentform:registration.value=remspecial(stritran(parentform:registration.value,"o","0"))

                  in the 'can depart' event and it seems to work.


                  michigan allows "1" and "L" and "I" in their license plates and the cops often get them screwed up... it's just the 'round thing' that they finally got settled and i think that might be nationwide (LEIN)...

                  what i'm doing is writing a parking ticket program - the officers will be responsible for entering their own tickets in the program so that should eliminate most of the mis-interpretations except for the officer not being able to read the plate.

                  i looked at the file developed so far (in a spreadsheet) and realized that 'the girl' had entered all the garbage put on the ticket by the cops and the registration needed a lot of cleaning for which remspecial is great.

                  i saw the potential trap with the onkey event and realized that i'd have to condition the event with not only "o" but also make sure the registration text box was active using "<OBJECT>.ACTIVE()"..

                  Comment


                  • #10
                    Re: restricting characters entered in text box

                    Now I know how I ended up with all these tickets!

                    Comment

                    Working...
                    X