Ken, you inspired me!

>If it were happening to me, I would tend to assume that something was happening to my VFP environment that I didn't know about or had happily assumed could not possibly have anything to do with the problem. Instead of hunting for things, I would probably rename config.fpw, delete all copies of Foxuser, open up VFP, do MODI FORM MyTest straight from the command window, open a method, and try the CTRL+F. If it still happens, I would find myself strongly considering rebuilding the machine from the OS up, but would likely try to think of something explainable before resorting to the nuclear solution.

twas the trying the modi form from the command window that put me on the right track. In a feeble attempt at saving a couple of keystrokes I typically dive into my project using a one line program which does "MODI PROJECT (MYPROJECT)"

Of course, the system then thinks of me as being within that shell program rather than in the project manager. And that is what appears to cause the rogue behaviour. (in that, if I just go in using the command direct, my find and replace behaviour works normally.)

This is exactly the problem one has with vfp and, presumably for the same reason. Of course, we still don't know what the reason is, but, frankly I don't give a damn as long as I can use the damn thing again.

Only one thing really does puzzle me. You might reasonably ask the question, why didn't I try that months ago? The answer is that for many months before I first reported the problem I had been going into the project manager in exactly the same way and NOT experiencing the find/replace problem, so it never occurred to me that my entry method might be the cause.

Thanks - you can imagine the relief!

Harry