>Hi,
>You know I've had the problem too. I've had "set deve on" and use both "clear all" and "clear program". Does anyone know what really causes this error to occurr? One time I tried to use touch and that work very time but was just to much trouble.

The single most frequent cause of the problem that I've seen has been software that is being worked on at various times with two systems whose clocks are badly out of sync. let's say that my clock is ahead of yours by a day. i make a change to the code and compile - the date/time stamp on the .FXP is based on my clock, so it's marked 12:10PM on 2/28/99. At 4PM today, you discover a bug in the code, make a change, but don't force a recompile; VFP will take care of that for you automatically when you go to run the code, since you made your change after mine, you'd assume that the date/time stamp on my compiled version is earlier than the last modified date of the program. So you fire up the debugger, point at the .PRG and let it rip - at which point, it sees that the date/time stamp on my FXP is later than the date/time stamp on the .PRG; there's no need to recompile...

This also happens when you go to debug an app and copy in what you think are the right versions of the .PRGs or .VCXs to make debugging work, and you then discover that the source doesn't match the p-code.