>I tried that and it works. I still don't understand why following the registry edit directions found in help still doesn't change the values. It isn't until you create a config.fpw file that overrides the values stored in the registry which are supposed to be resettable by using the "set default button", that the entries are set for the session. Thank you for your help

PMFJI: I'm not entirely sure of the reason, but FWIW I think its related to old DOS pathing on FoxPro/VFP internal loading events... I have also had the problem, and solved it much as was suggested above, but I did have the old FP directory in the DOS path from Autoexec.Bat or network login script assignments. When on other machines without FP in the path or login script, all worked as it should. It seems to me that the registry entry should be enough for VFP, but as we have found, that ain't always so...

Rob