Special Mask

[Kevin G. Timberlake]

I have done this a long time ago but cannot find where it was on the threads.

I need to mask a field that will look like this:
X-XX-XXX-XX-XX-XXXXX when the user inputs 123456789012345

The end result being: 1-23-456-78-90-12345

Any advice?

[Keith Hubert]

Re: Special Mask

Hi Kevin,

Have you looked in Field Rules, Data Entry?

[CALocklin]

Re: Special Mask

Any advice?

Here's my attitude towards masks - and remember what you paid for it.

I seldom use masks anymore. Instead, I create a function that changes the input value as necessary. This function is used in the CanWrite event of the field and to "fix" data input by the user in other places.

Example:

I have a Phone_dash() function that converts 7 character numbers to something like:
123-4567
and anything larger to:
123-456-7890

In fact, if the user types any of the following:
1-1234567 or
11234567 or
1-(123)4567890 or
1#(123)-456-789-0%
the result will still be:
123-456-7890

As you can see, this function is much more versatile than a simple mask - and it will get even better if you read on....

If the user goofs and enters an 8 digit phone, the result is:
123-456-78
If it's longer than the typical 10 digit number, it's:
123-456-78901234

Now, here's the part the users really like. I can create a Find that asks for the phone number, they can type 1234567 and my Phone_dash() function will change it to the correct format before running the find action. Something like this:

ph = ui_get_text( "Phone Number", "Enter phone number to find:" )
IF ph = ""
    END'
END IF
ph = phone_dash( ph )
parentform.find( ph )

This eliminates any concern about the user (a) remembering to type the number in the correct format or (b) remembering what the correct format is. It also eliminates the need for the user to find/press the special character keys which makes data input slightly faster.

My users really like this feature.

I almost forgot. The field's CanWrite event (in the table - not in the form) is really complicated. It looks something like this:
A_field_value = phone_dash( A_field_value )

[Kevin G. Timberlake]

Re: Special Mask

Yeah Kieth, I have been racking my brain on it in just about every "easy" way I could. Cal, I am going to give your a shot too. I do need to have the user be able to do a report specifically on this number, so the search will come in handy for sure...

[Kevin G. Timberlake]

Re: Special Mask

Well, I have no idea of what I just did, but it works. In the data tab of Field Rules I did this:

Conditional Mask = #-##-###-##-##-##### "Conditional upon" LEN(ALLTRIM(CUSTOMER->BILL_STATE_REGION))<3.OR.CUSTOMER->BILL_COUNTRY="".OR.CUSTOMER->BILL_COUNTRY="USA"

I simply copied the condition from a phone mask changing the result to what I needed. I am horrible at the scripting since I had been away from A5 for so long...But it works!

[jkukuda]

Re: Special Mask

Very informative thread, Thanks

[Kevin G. Timberlake]

Re: Special Mask

Well now this seems to be interesting. I went back to a different table to create the same mask and all I had to do was go to field rules/data entry/"simple mask" and type in #-##-###-##-##-#### and it worked. Now I tried this in other tables and it never worked. So I have no idea why it does now, but, it works like it was supposed to. Alpha has proven to be a more detailed rad than Filemaker, my only issue has always been the same thing...new updates and releases...new bugs... Don't get me wrong, I have used Alpha since V6 and Filemaker since V6 and they each have a lot to offer. It just depends on what YOU are willing to be frustrated with ;)