An old topic I know, but it never did stop bugging me this one (and any number of calls to vfpclean.app did nothing for me btw)

I got angry at this bug the other day, not the first time, but hopefully the last, and spent a day uninstalling foxpro, reinstalling it, running vfpclean.app, clearing registry settings and all sorts of other fun things.
(also searched here extensivley hoping that someone had eventually found out the cause of this)

during all this I noticed something though.
If I started foxpro, with a project open, it would C5, if I started foxpro with no project open, and had to open it myself, it would not C5.
Following this line, I found that issuing a CD or CHDIR . command when i first entered foxpro would stop it C5'ing.
so i added

COMMAND= CHRDIR .

to my config.fpw files and have not had a C5 since.
Take it out and it does C5.

I had managed earlier in the day to stop C5's without this line, through changing my windows path around. I then tried to get a test case from it, and broke my windows path again, it C5'd, fixed the path, it C5'd... That confused me slightyly, but may of aided in the fixing.

If there is anyone still suffering this bug, would you mind giving the above a try and see if it fixes the problem for you, i would be interested to know if it is a one off fix for my machine or works for other people aswell.
I also hope it has been fixed in vfp8.0

Thanks,
Chris