Hi David,

We reinstalled FoxPro, and it worked for a little while. Then the problem came up again.

It seems to be associated with the debug window. We discovered that the problem only occurs when the debug window is open.

I remember that there was another weired bug that had to do with the autocomplete, that crashed FoxPro anytime you put in the closing bracket of a method. That also appeared out of nowhere, and I don't know if anyone ever figured it out. A workaround was to change the directory as soon as you opened FoxPro. Don't ask me why, but it worked!!!!

I hope there is some type of workaround for this one also, and that someone else has figured it out.

Steven

>Steve,
>
>I've never seen anything like this, or seen it reported for that matter.
>
>Is there some ON ERROR handler that's actually perturbing things?
>
>>I ran into a weird problem on one of my developer's machines. Suddenly, today, all methods return .T., regardless of what values they are supposed to return! Naturally, this crashes the whole application, as no proper values can be returned by anything.
>>
>>To make myself clear, say that I have the following code:
>>
>>? getValue()
>>
>>FUNCTION getValue
>>RETURN 'Hi'
>>
>>This code, surprise, surprise, returns .T., NOT 'Hi'
>>
>>It has nothing to do with the code. We copied all code from a machine that is working, and the problem is still there. We also tried the above program, and it keeps returning .T. anytime we try it. I am presently reinstally FoxPro 8 to see if it will help.
>>
>>Has anyone seen anything like this before? Any chance someone has actually resolved it?
>>
>>Steven