Indeed, SET ANSI appears to make the difference. However, there is no mention about SET ANSI at all in the documentation of ASCAN. If it's not a bug in ASCAN, then it is a major shortcoming in the documentation. If you all here agree, then I will make a bugreport about it and let the vfpt decide whether the function should change or the doc.
>Hi Peter,
>
>It looks like VFP uses internally a single routine to compare strings. Both, the "=" operator and ASCAN() seem to call this function. Therefore, inside a SELECT statement ASCAN() compares string according to the current SET ANSI setting. If you insert SET ANSI ON right before the select statement, you get the same result as with the SCAN loop.
>
>BTW, you should add NOFILTER to the second SELECT statement. Otherwise, the code runs eternally, because VFP creates a filter.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
