Patricia,

When it happens to me I'm usually in and out of the class/form designer and having the debugger popup while doing development. Most of the time it happens to me with .prg files that are stored in the .. directory, ie one level up from the project directory.

If you can ever isolate a specific sequence of events that'll cause it to happen MS would love to get them so this bug can be fixed, but it requires a reproduceable sequence for them to duplicate it.

>Like you say, shutting down VFP & restarting is the only way that I have found around this problem so far which thus sounds very much like a subteranean (is that how it's spelt?) bug :)
>
>I have wondered if this problem is a factor arising from a certain combination of events such as of canceling program operation will using the debug tools; i.e. perhaps some part of the debugging mechanism puts a file lock on the program fxp file (though I cannot imagine why it would so do) and then fails to release under certain conditions - but this is pure speculation based only upon the apparent propensity of this problem to appear only after invoking debug and using it for a succession of trial runs whereas it does not seem to occur under none-debug mode conditions. It certainly has nothing to do with any of the conditions attributed to error 102 since - as admin - I have all the necessary file permissions, etc & hence error 102 is really erroneous in this case.
>
>Who knows, maybe someone else out in UT land has an explanation but at least we have agreed upon the sledgehammer resolution - close and restart!!! ;~( Unfortunately, no way around the frustration nor the waste of time; yuk. Thnx.