Oh, and while I'm at it, I had another PATH related issue come up the other day. Again, I was adding something to the path and I issued a "? SET('PATH')" command and the folder I added was not in the path. I checked and rechecked the syntax and it should have worked fine. What I discovered was that I was getting fooled by VFP. The command had worked, but when I used "?" to display the path, VFP just truncated the display at a certain point. And not in the middle of a folder name, but after a semicolon, which made it look like the path was legit, but just didn't include my addition. Perhaps I should have been clued in when I also noticed that the last folder at the end of the path before I attempted to add a folder was removed. It looked like a bug or something (and I do think this truncating behavior is not proper). Even now, it will not display my full path. It truncates it and refuses to display the whole thing. I assume it would wrap it to the next line and - strangely - I believe I did get it to do this, but sometimes it does and sometimes it doesn't. It seems to be related to the length of the path - when it's in a certain range it truncates, but if it goes over that range it then decides to word wrap it and I can see the entire path without anything being left off.

>VFP doesn't read path from the Windows. Those entries had to be added by something or someone. You can safely remove them.