>Hi Al - it has been something that has plagued me since I first used vfp in 1998, so I don't think it is anything in my environment doing it. I am, just surprised nobody else seems to know about it..

You've probably already heard these, but I'll repeat them anyway. Some things you can check:
* Check to see if you've got ClickLock enbled -- this can do strange things at times
* Check the double-click speed -- having it too slow or too fast can do weird things
* If you've enabled profile that automatically double-clicks icons with single click -- that sometimes does weird things.
* Check mouse profile and turn off feature (if present) that automatically selects windows when you "float" the mouse over it -- this could do weird things on occasion.
* If you've got "Snap To" (automatically move pointer to default button in a dialog box) can do strange things.
* Some mice have a profile setting to change meaning of when you click down on the wheel or tilt the wheel (if the mouse has that feature) -- check to see what those functions are mapped to.
* Some mice have extra button other than the usual left, right and wheel -- these additional buttons might cause unexpected things to occur if you're not careful.
* If you've got a wireless mouse, you might get spurious inputs when the batteries start running out.
* Wireless mice and keyboard may act weirdly if you put computer under desk -- especially if you've got a metal desk

As for the behavior you describe, I've not encountered that -- though in VFP6 I did get an occasional display "glitch" where some of the lines displayed in the text editor would not display properly -- sometimes the lines would appear indented, and sometimes not, and other times lines or portion of lines or entire lines would appear to be missing. Hitting PgUp and PgDn to force a repaint would often get around the occasion glitch -- at least temporarily. Once I got the display glitch, it would tend to happen more often as long as I stayed within the same session. Usually exiting the VFP IDE and re-starting it would avoid getting the problem for a much longer period.. It didn't happen too often -- once every few months or so -- just enough to get annoying, but not enough to be too worried. I've also noticed that running a program within the IDE was more often to result in the problem than if I kept two separate sessions (one where I'm using to edit and compile) -- and the other to run within debugger. On the upside is by keeping separate sessions, it was easier to do a controlled shutdown of the IDE where I may have program files opened than if I was using a single VFP session.