>>I have a line of code that has suddenly, after two years, turned on me. It is, simply:
>>
>> Select 0
>>
>>It is now sporadically returning a Data type mismatch error.
>>
>>This is in FPW 2.6; anyone have any ideas? Yes, the 0 is a zero, not an O.
>>
>>I have a similar strange error with these lines:
>>
>> If Used('Qpers')
>> Use in Qpers
>> Endif
>>
>>This is also returning a data type mismatch, on the second line.
>>
>>This is a mature application, and I haven't changed anything in either of these two routines, so it has to be something external that is affecting this.
>
>Two guesses here:
>
>The application has become corrupted or FoxPro has become corrupted.
>

Craig, I would investigate the previous command/line Also, some times I have seen when viewed with a hex editor My prgs have a 20... Well anyway it looks like a space but it is not and foxpro reads it that way. You can also try to retype the sele 0 on the next line (no cut'n'paste) then delete the existing line.

HTH