>>>>But the
>>>>SET ORDER TO TAG MyField2 does not produce error. Yet I don't see the tag MyField2 in the list of index tags. Also, the status line of VFP shows that the tag is set to MyField1 (not MyField2).
>>>>Weird.
>>>
>>>Interesting, looks like you found a bug in VFP. I am able to duplicate this problem. The command
>>>set order to tag FieldName -- no such tag
>>>does not result in error, although the order is not set.
>>>
>>>May be it's even documented and if not, clearly a bug which you discovered now (unless it was already discovered).
>>>
>>>It is not documented in SET ORDER command, I just read it.
>>
>>Here is what I plan to do. I will create this index tag so that the command will match the existing tags. The way I came across this problem is I did plan to have this index tag. But forgot to create it. Yet, my meta table has this index tag. So in one process the program uses meta table for index tags; set the index tag (using SET ORDER TO TAG ...) and then goes to the last record (GO LAST). Yet, I was not getting error on my machine. Except a customer is getting an error. So it must be something specific to my machine that does not show the error.
>
>In my tests if you try to SET ORDER TO FieldName which does not have the actual tag, I am not getting an error (in IDE). You need to test it in IDE vs. exe and also compare all settings as it could be a setting that affects this behavior.

On a related subject, do you think the following code is the best way (programatically) check if a CDX has a certain index tag:

Function TagFound
lparameter cTagName
local lRetVal
lRetVal = .F.
FOR nCount = 1 TO TAGCOUNT()
   if tag(nCount) == cTagName
      lRetVal = .T.
      exit
   endif 
ENDFOR
return lRetVal