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

Regular Expression problem

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

  • Regular Expression problem

    I am using a regular expression to validate a South African Identity number in a dialog. When I test using the test value option in the field validation dialog it works but when I try it in working preview or in the browser the validation fails. This the expression
    Code:
    (((\d{2}((0[13578]|1[02])(0[1-9]|[12]\d|3[01])|(0[13456789]|1[012])(0[1-9]|[12]\d|30)|02(0[1-9]|1\d|2[0-8])))|([02468][048]|[13579][26])0229))(( |-)(\d{4})( |-)(\d{3})|(\d{7}))
    . Validates correctly in the field validation dialog, A.PNG. When I test it in Working preview it gives me an error. AA.PNG. Where am I going wrong

  • #2
    Re: Regular Expression problem

    Jaco,

    I applaud your efforts at trying to code this, but Alpha can make this job much easier for you. If you have a list of valid numbers, you can then store them into a small database and use validation to check them there. While Alpha will allow you to use code like this, it is quite confusing and a horror to debug. What happens later when you want to make a change or update something?

    Comment


    • #3
      Re: Regular Expression problem

      Hi Charles.
      Thank you very much for your advice. The regular expression is given by the Department of home affairs in South Africa and is used by numerous applications to validate South African citizens identification numbers. It is highly unlikely that it will change. I don't understand your proposed solution to check against a small database. I will really appreciate it if you could elaborate and maybe give a small example

      What is strange about the expression is that it works fine in a grid. It only fails in a dialog

      Comment


      • #4
        Re: Regular Expression problem

        Leading or training spaces will cause the expression to fail. "7403115084088" will validate while "7403115084088 " will fail. Depending on the build, the dialog should strip the spaces. The validation works fine in the current release build with the value in the image.

        Comment


        • #5
          Re: Regular Expression problem

          Hmmm. I tried it and it validated in test for me and in a grid with detail. So I can confirm it is working. Do you have the field set for the correct number of characters in the dialog? In one of my iterations, I didn't do that and it failed.

          Charlie

          Comment


          • #6
            Re: Regular Expression problem

            Sorry Jerry! We both responded at the same time!

            Jerry is correct. Try trimming the function with Alltrim().

            Charlie

            Comment


            • #7
              Re: Regular Expression problem

              Thank you Charlie & Jerry. I currently run version 2873, build 3990. It doesn't strip out the trailing spaces. I did however validated length and this sorted out the problem

              Comment

              Working...
              X