I WISH :O)

Sadly, no. It must be easily typed WHILE the user is hearing the information over the radio. The individual passing the information to the user over the radio may say it in any order and for the data entry operator's speed and ease of use, the user must be able to type it in any order without having to enter identifiers of any sort. The user should only have to separate the fields with commas but needs to be able to enter the information in any order, and if the values pass muster (another check for each control follows the code I posted earlier which verifies the data in each field is valid) then focus is set to an ok button. If any field does not pass, then focus sits on the first control which fails. For instance, if an invalid location is entered, then focus will sit on the location control when the form is instantiated. Those checks are done mostly like:

Also, I neglected to mention that this is one of hundreds of commands the user can type and it cannot include identifiers because none of the other commands require it.

CASE THISFORM.state.controlrequired .and. EMPTY(thisform.state.value)
   thisform.state.setfocus()

*OR SOMETHING SIMILAR TO*

CASE !EMPTY(THISFORM.state.value) .and. !thisform.state.lostfocus() 
   thisform.state.setfocus()

*--Each control's lostfocus may or may not call a function to check the value in the control

However, before the latest round of changes, there was no visible delay in the form instantiating. Since I started checking for the single and double quotes and for the year each and every loop, it has slowed down. I can not see any way around checking for those every loop though but then I have looked at this too much recently and I need to step back and come back to it I think. I probably need to change the way I look at the requirements and how the processing goes...

>Hi Tracy.
>
>>Later it was decided that the user should be able to enter the values to populate the fields in any order after the TS is typed.
>
>Is it possible to add one thing to the specs: the need to type an identifier for each parameter? For example:
>
>B10 TS L=4004, A=100 N Main St, S=TX ...
>
>where L stands for license, A for address, etc. That way, the user could type things in any order they wish and the parsing would be easy and fast using STREXTRACT(). And a single mnemonic letter or at most two letters would be easy for the user to remember.
>
>Doug