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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Field Masks not working with lookup() function

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Field Masks not working with lookup() function

    I have a table that defines several simple masks via field rules, e.g. phone no. and postal code, with the mask literals set not to be stored. When entering data directly via the keyboard the masks are correctly displayed. However, I have a routine whereby field content must be entered by means of the �Set Field Values� action script. This script in turn uses expressions incorporating the lookup() function to fetch the appropriate field value(s) from another table. The table called by the lookup() likewise defines the same simple screen masks in its field rules for the matching fields. See the attached screenshots. Mask1 shows correct masking results when data is entered via keyboard. Mask2 shows the lookups correctly get the desired data and set the appropriate field values; but the results do not get displayed with the defined masks. If the data originates via the lookup() then the masks seem to be completely ignored. And not just relative to the form where the lookup() was used, but for all other forms or browses where the same fields are displayed. See Mask3, a default browse generated after using the lookup() to set the values.

    Is there some way to force the masks to be properly displayed in these instance or am I going to have to save the mask literals in the table(s) from whence the lookups are fetching the values?
    Tags: None
    #2
    Re: Field Masks not working with lookup() function

    Originally posted by DRW View Post
    I have a table that defines several simple masks via field rules, e.g. phone no. and postal code, with the mask literals set not to be stored. When entering data directly via the keyboard the masks are correctly displayed. However, I have a routine whereby field content must be entered by means of the ‘Set Field Values’ action script. This script in turn uses expressions incorporating the lookup() function to fetch the appropriate field value(s) from another table. The table called by the lookup() likewise defines the same simple screen masks in its field rules for the matching fields. See the attached screenshots. Mask1 shows correct masking results when data is entered via keyboard. Mask2 shows the lookups correctly get the desired data and set the appropriate field values; but the results do not get displayed with the defined masks. If the data originates via the lookup() then the masks seem to be completely ignored. And not just relative to the form where the lookup() was used, but for all other forms or browses where the same fields are displayed. See Mask3, a default browse generated after using the lookup() to set the values.

    Is there some way to force the masks to be properly displayed in these instance or am I going to have to save the mask literals in the table(s) from whence the lookups are fetching the values?

    Are you sure the table being looked up has the phones masked as you say in the red highlighted. You did not show us that in a picture. The attached example shows no issue with this.
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment

      #3
      Re: Field Masks not working with lookup() function

      Mike, thanks for your response. Yes, I double checked all the field rules pertaining to masks for the involved files and they are there. Because the routine I am using is buried down in the bowels of a large, complex application, I will need to spend some time to reduce out the relevant pieces for some further testing and then, depending on what I conclude, perhaps post the results here in the form of a zipped example. Will get back with what I find.

      Comment

        #4
        Re: Field Masks not working with lookup() function

        So I finally got A5 to properly respect masks applied to fields that were getting their data values set using lookup() functions. Mike's example clearly showed that the masking does work correctly, although in my examples it didn't.

        So, I ripped my app/routine down to the barest essentials to try and deduce the source of the glitch. Finally concluded that there was some sort of corruption in the datafile with respect to how A5 was interpreting/applying screen masks and the attribute setting for storing or not storing the literals in the file. Odd that the corruption only affected the masking and nothing else - and that it did so for all fields using masks in the same file. The final fix? Delete the file from the application and build a complete new idenical version; not the data, but the field definitions and field rules. Voila, problem solved.

        Thanks again Mike for taking the time to confirm that the masking should indeed work.

        Comment

        Previous template Next
        Working...
        X