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

Store mask literal behavior

  • Filter
  • Time
  • Show
Clear All
new posts

  • Store mask literal behavior

    Declared a social security number field of char length 9 in a table, and applied a mask of 000-00-0000 and applied the check box "do not store mask literals in field". Default browse and forms using this field do not allow me to enter the entire number in the field. It will allow me to enter 123-45-67 and disallows any further entry. I tried to change the input width on the form to 11, but that didn't work either.

    I can enter the entire field if I redefine the field length to 11, but that seems wasteful, and suggests that the 'do not store' option is pointless.

    Am I missing something here?

  • #2
    Re: Store mask literal behavior

    It seems that no matter what you check on the field rules "do not store literals in file", they are still being stored - therefore a social security number would need to be 11 to accept the number and the "-".

    There has been other discussions on the masking field rule. I went back to version 7 and it appears that the field rules as far as the literals in the stored field are the same. They are always stored.

    I don't use masks that often so I would not have noticed until your post.

    Maybe others will join in and test the field rule on masking and inclusion of literals.



    • #3
      Re: Store mask literal behavior

      It occurred to me that declaring the field character may have been messing with the mask literal interpretation of character vs. numeric. I changed my field type to numeric length 9. It made no difference. I could still only enter 123-45-67.

      Before I even posted the initial message, I did the obligatory search for previous answers on this topic but had no luck.


      • #4
        Re: Store mask literal behavior

        The post I was talking about was

        It was relative to the placeholder character.

        In that post it was pointed out that in Version 6 the masking was changed - but it did not mention "Do not store the literals"

        I have tried every type of mask I could think of and checked the "Do not store" but the mask was stored with the record.

        I don't think that this is a bug, but a change made that has never been documented in the help files such as the conditional mask - which should be ignored (from that post also)

        Evidently the help files and the field rules on masks are wrong.