Hi - I had a problem, to which I've already found a solution (ableit a slightly unexpected one). I'd appreciate some feedback though, as to whether I've missed anything obvious .. or whether what I'm attempting to do can be achieved more easily in A5 v10 (I have A5 v9).
Problem : To force entries in a character field into UPPER case as the user types, whilst allowing spaces, brackets and other symbols.
First attempt : Use the Field Rules, selecting "Case Convert". However, this accepts characters in lower case then transforms them once the field is complete .... which I find Messy !
Second attempt : Use a simple Mask in the Data Entry options. I selected 'N' for every character in the field as the Help file says this allows ... [N = Any uppercase letter, digit, sign or decimal]. However, it actually disallows spaces and other symbols such as brackets (only allows letters and numbers) .. and in addition only pushes the first character of the string into Upper case !
Third attempt. Using an excellent function from Ira Perlow (Keyboardstate), I detected the status of CAPS LOCK. If the keyboard is in lower case mode, I switch the keyboard into 'CAPS LOCK ON' mode temporarily for Data Entry purposes using sys_send_keys("{CAPSLOCK}").
All of this seems a bit of an overkill for what should in my opinion be a staple choice for field entry (either in the dictionary or an form level). This contrasts markedly with other database / development systems I've used in the past which have an option to force Upper Case at the field-entry stage.
Some questions then - 1) Have I missed something obvious, particularly with regard to my understanding of the Mask facility in Field Rules and 2) If not in v9, is the faciilty I'm after available in v10 ?
Depending on your responses, I've a feeling that this may end up in the Features-Wishlist pile !
Regards to all, Jem
Problem : To force entries in a character field into UPPER case as the user types, whilst allowing spaces, brackets and other symbols.
First attempt : Use the Field Rules, selecting "Case Convert". However, this accepts characters in lower case then transforms them once the field is complete .... which I find Messy !
Second attempt : Use a simple Mask in the Data Entry options. I selected 'N' for every character in the field as the Help file says this allows ... [N = Any uppercase letter, digit, sign or decimal]. However, it actually disallows spaces and other symbols such as brackets (only allows letters and numbers) .. and in addition only pushes the first character of the string into Upper case !
Third attempt. Using an excellent function from Ira Perlow (Keyboardstate), I detected the status of CAPS LOCK. If the keyboard is in lower case mode, I switch the keyboard into 'CAPS LOCK ON' mode temporarily for Data Entry purposes using sys_send_keys("{CAPSLOCK}").
All of this seems a bit of an overkill for what should in my opinion be a staple choice for field entry (either in the dictionary or an form level). This contrasts markedly with other database / development systems I've used in the past which have an option to force Upper Case at the field-entry stage.
Some questions then - 1) Have I missed something obvious, particularly with regard to my understanding of the Mask facility in Field Rules and 2) If not in v9, is the faciilty I'm after available in v10 ?
Depending on your responses, I've a feeling that this may end up in the Features-Wishlist pile !
Regards to all, Jem
Comment