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 or format rule for email

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

  • Mask or format rule for email

    Has anyone every done a custom mask for an email? An example of what I'm looking for is as follows:

    [email protected]

    What I'm trying to do is making sure that the "@" sign is present and the "us.dka.com" is in the right format. Maybe a Mask is the wrong thing. Potentially a script that would validate would be the better way to go.

    Thanks,

    Ryland

  • #2
    Re: Mask or format rule for email

    Originally posted by [email protected] View Post
    Maybe a Mask is the wrong thing.
    It is.
    Originally posted by [email protected] View Post
    Potentially a script that would validate would be the better way to go.
    Not necessarily a script but a regex expression. This was discussed in details in another thread. I will see if I can locate it.

    This one.

    Comment


    • #3
      Re: Mask or format rule for email

      You might not even need a regex expression if all you want is to confirm that it ends with: @us.dka.com"
      Code:
      x="[email protected]"
      ?right(x,11)="@us.dka.com"
      = .T.

      Comment


      • #4
        Re: Mask or format rule for email

        Thanks...I found one of the earlier posts that you pointed me to, and it is doing the trick... the format that appears to work fine is:


        ' Regex expression got this right
        ?regex_match("[email protected]","\b[A-Z0-9a-z._%-][email protected][A-Z0-9a-z._%-]+\.[A-Za-z]{2,4}\b")
        = .F.

        so I changed my variables to match the example with a conditional variable names "user" and it working great.


        if regex_match(user,"\b[A-Z0-9a-z._%-][email protected][A-Z0-9a-z._%-]+\.[A-Za-z]{2,4}\b")= .F.
        msgbox("Invalid email Format - Please Re-enter")
        end
        end if

        Thanks, Ryland

        Comment


        • #5
          Re: Mask or format rule for email

          Hey Guys,

          Maybe I am being too simple here or misunderstanding what was needed, but if all you want to do is make sure a email address is properly formatted why not just use A5_EMAIL_VALID()?

          The A5_EMAIL_VALID() function determines if an email address is properly formatted. It does not validate the address itself.


          Scott

          Comment


          • #6
            Re: Mask or format rule for email

            Hi Scott,

            I tried that earlier, but since I have additional periods in between the first name , middle initial, and last name, as well as after the @ that function wasn't working for me. This last set if code checks for them and seems to be ok for now. Thanks, Ryland

            Comment


            • #7
              Re: Mask or format rule for email

              Hummmmm .. the function seems to work fine for me.

              Code:
              x = "[email protected]"
              ?a5_email_valid(x)
              = .T.
              
              ?a5_email_valid("[email protected]")
              = .T.
              Maybe there was something else going on that made it not work ... In any case, if your happy with what you have then thats what counts.

              Scott

              Comment


              • #8
                Re: Mask or format rule for email

                Originally posted by Scott Emerick View Post
                if all you want to do is make sure a email address is properly formatted why not just use A5_EMAIL_VALID()?

                Scott
                He wants to validate a specific domain not just validate the email.

                Comment


                • #9
                  Re: Mask or format rule for email

                  Originally posted by Scott Emerick View Post
                  Maybe I am being too simple here or misunderstanding what was needed, but if all you want to do is make sure a email address is properly formatted why not just use A5_EMAIL_VALID()?
                  FYI: Careful about assuming too much with A5_Email_valid(). All it really checks is that there is an @ sign and a period after the @ sign but not at the end of the email address. According to A5_Email_valid(), these are all acceptable:
                  Freddy#[email protected]
                  [email protected]
                  [email protected]
                  Freddy.*@somewhere.xqr
                  [email protected]

                  Even the regex method won't catch the ones with a period on either side of the @ sign. (I don't think that's allowed but haven't been able to verify it. I certainly don't recall ever seeing anything like that.) Maybe someone knows (a) if a period is allowed on either side or the @ sign or (b) how to fix the regex() method to reject it?

                  I'm not very good with the regex() command but adding this seems to work for rejecting the period before the @ sign:
                  regex_match("[email protected]","\b[A-Z0-9a-z._%-]+[A-Z0-9a-z]+@+[A-Z0-9a-z._%-]+\.[A-Za-z]{2,4}\b")
                  But I can't figure out how to check for it after the @ sign and still allow a one letter address like "x.com". (I think that's legal???)

                  Since I already had to build my own UDF, I don't need a regex() solution but it might be useful for others. Unfortunately, I came here to find a method I could use in A5v5 but neither of these - regex() or A5_email_valid() - works in that version so I had to write my own UDF.

                  Comment

                  Working...
                  X