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



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 for Zip Codes

  • Filter
  • Time
  • Show
Clear All
new posts

  • Mask for Zip Codes

    Hi Everyone
    I have a customer form with a zip code field I made a mask
    of 00000-0000 and I want it to be 00000 only if the zip code
    is 5 I tried to make a conditional mask and cant get it to work

    Any help
    Thank you

  • #2
    RE: Mask for Zip Codes

    I suggest you make 2 fields; 1 for the first 5 and another for the last 4. Then you can concatenate the fields for letters, reports, labels making printing of the - dependent on whether there is anything in the 4 character field. It's easier to put fields together than it is to separate them later.


    • #3
      RE: Mask for Zip Codes


      If your customer uses these ZIP codes for addressing and/or mailing purposes, they will want to keep their ZIP in a single 10 chatacter field. First of all, that's what every piece of PC mailng/CASS coding and PAVE presort application is going to be looking for when processing. If your ZIP field isn't set up that way, some one will have to convert it in the mailing process.

      If you are writing an expression for a conditional field you might make it (or the equivalent statements if using the Field Rules section): if(len(alltrim(ZIP)) = 5, 00000, if(len(alltrim(ZIP)) = 10, 00000-0000, [place alternative here])); you could also include 9 digit strings (ZIP's missing the "-") with: if(len(alltrim(ZIP)) = 5, 00000, if(len(alltrim(ZIP)) = 9, 00000-0000, if(len(alltrim(ZIP)) = 10, 00000-0000, [place alternative here])).

      If you try to make a conditional field conditional on itself (a logical way to format your data) Alpha Five won't recalculate the new value when you leave the field and move on. If you were to go back to that field and then move on once again, it will recalculate correctly. It will only work the way you expect if you are basing your conditional calculation on info contained in another field. (Frustrating, I know, but I'm told that this will be corrected in version 5.)

      It's also possible that you could write it in XBasic as an OnDepart or OnChange event for that field, but I haven't tried it myself.

      Once agian, if your client is going to use the ZIP for mailing, the table will still have to be CASS coded by you or the mailing house before it can be processed anyway. If you are doing this in house, just have your data entry people enter the 5-digit ZIP and the coding software will put the correct +4 extension, standasrdize the address, add carrier routes and lines of travel, etc. (most people don't accurately know their +4's anyway).

      If you are having the mailing house do this, tell them to give your client back a file with the ID's, address(es), cities, states, and ZIP's. Post the new addressing data back into the table using the ID's (original and returned) as the link between your tables. Bada Boom, Bada Bing, it's clean, correct and updated -- not only with correct ZIP+4's, but also with correctly written addresses, etc.

      Hope I didn't get too far off the topic...

      Best regards,

      Geoff Hollander


      • #4
        RE: Mask for Zip Codes

        Hi Geoff,
        Can you input into 2 separate fields (for ease of use) and then combine them into a calculated field for mailing or is that not practical?


        • #5
          RE: Mask for Zip Codes

          Hi Ray

          I don't use a mask. What I use is a field rule event CanWriteField. Here is the code.

          ''converts U.S. and CANADIAN postal codes to the correct format
          option nobreak
          option strict
          dim shared a_field_value as c
          dim code as c 'temporary or local variable


          ''converts U.S. and CANADIAN postal codes to the correct format
          option nobreak
          option strict
          dim shared a_field_value as c
          dim code as c 'temporary or local variable


          case LEN(remspecial(code))=9
          case isalpha(code).and.len(remspecial(code))=6
          code=substr(upper(remspecial(code)),1,3)+" "+substr(upper(remspecial(code)),4,3)
          case len(remspecial(code))=5
          case else
          end select


          • #6
            RE: Mask for Zip Codes

            oops....! Sorry about the slopy paste job.