Harry,

>thought I remembered you from my futile attempts at vpm!

Yes, it's me. Glad to know I wasn't the only one who went half-crazy with that after the glow wore off.

>
>you might be right but for the wrong reason! I know the vpm behaviour and its one of many reasons I dropped it. ...... I never use it. So the behaviour I'm describing is pure vfp behaviour.
>
>Unless, that is, you are suggesting that merely having vpm installed might be enough to "infect" vfp...
>

It's a long stretch to assume VPM is somehow affecting your behavior just by existing. If that could happen, we'd all have long ago been destroyed by Word macor viruses <s>.

But, since we're both familiar with the VPM behavior, it gives us something to go on. The question on my mind is, could something *else* similar to VPM be hooked into your VFP installation that's having the same effect?

My reasoning is as follows:
1. I doubt very highly that the OS could be causing this, so we'll put that idea on the very furthest back burner.
2. Since you've de/reinstalled VFP and SP3, we will assume that VFP is clean.
3. This leaves only the VFP environment. We both have experienced VPM's oddities and know that the environment can cause these things, so I would ponder: Is this really and truly absolutely completely (and I mean it) clean?

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.