Calvin,
I think the Help File probably explains this
Quote
nIndexNumber
Specifies the number of the controlling index file or tag. nIndexNumber refers to the index files as they are listed in USE or SET INDEX. Open .idx files are numbered first in the order in which they appear in USE or SET INDEX. Tags in the structural .cdx file (if one exists) are then numbered in the order in which they were created. Finally, tags in any open independent .cdx files are numbered in the order in which they were created.
endquote
so tag(6) may not always be recnums
I would suggest that you just "Set order to recnums"
Regards
>Some of you may have been following the tread about weird behavior associated with an index tag named recnum. On 2 machines an error would be generated to the effect that the index did not exist. Subsequent to writing that thread I renamed the tag to recnumS. On at least 1 machine when it is run with the Exe on the workstation and the data on the server the problem resurfaces. If is is run so that the exe and the data are on the server then it works ok. (the exes are identical) I changed to code so that it now reads:
>SELECT wpsctran
>IF LOWER(TAG(6))='recnums'
>SET ORDER TO tag 6
>else
>SET ORDER TO tag recnums
>endif
>
>This code works everywhere. I cannot for the life of me figure out why this makes any difference since in either case the tag is being set to recnums.