>>>>I have recently bought a new computer. Previously I had installed Visual FoxPro in the following folder: C:\VFP. When I installed Visual FoxPro on my new computer, it wanted to be installed in
>>>>C:\PROGRAM FILE\DEVSTUDIO\VFP and I accepted the default location.
>>>>
>>>>In the past, it has been my practice to create shortcuts on the START menu and on the Windows desktop that will launch versions of VFP with an environment suitable to the project on which I plan to work. I would accomplish this by writing a custom configuration file, saving it in the HOME() folder and using the -c switch in the target string of the shortcut to point VFP towards the custom configuration file. Here is a sample target string:
>>>>C:\VFP\VFP.EXE -CC:\VFP\CUSTFILE.CFG
You might also try the FOXPROWCFG environment variable, for example make a shorcut to a batch file. Let's say that you want to start up VFP in your development directory in one case and in a custom app dir another time. You might have 2 shortcuts pointing to VFPDEV.BAT and VFPCUSTOM.BAT
in VFPDEV.BAT might have

@echo off
set foxprowcfg=c:\vfp\dev\config.fpw
start vfp

in C:\VFP\DEV\CONFIG.FPW

RESO=ON
EXCLU=ON
DEFAULT=C:\VFP\DEV

in VFPCUSTOM.BAT might have

@echo off
set foxprowcfg=c:\vfp\customapp\config.fpw
start vfp

in C:\VFP\CUSTOMAPP\CONFIG.FPW

RESO=OFF
EXCLU=OFF
DEFAULT=C:\VFP\CUSTOMAPP

I havent actually tried this yet, but it's a thought that may help! Let me know if it works //:^)


>>>>
>>>>Now that VFP is installed in the C:\PROGRAM FILES\DEVSTUDIO\VFP folder, I haven't been able to successfully point it toward a custom configuration file. I can write code in the default configuration file CONFIG.FPW and it will execute when I launch VFP from a shortcut with a target string, surrounded by quotation marks, that doesn't contain the -c switch. For example: "C:\PROGRAM FILES\DEVSTUDIO\VFP\VFP.EXE".
>>>>
>>>>Unfortunately, when I use either of the following strings in the shortcut target:
>>>>"C:\PROGRAM FILES\DEVSTUDIO\VFP\VFP.EXE" -CC:\PROGRAM FILES\DEVSTUDIO\VFP\CUSTFILE.CFG
>>>>"C:\PROGRAM FILES\DEVSTUDIO\VFP\VFP.EXE" -C"C:\PROGRAM FILES\DEVSTUDIO\VFP\CUSTFILE.CFG"
>>>>Visual FoxPro launches, but a messagebox immediately pops up saying "'custfile.cfg' does not exist".
>>>>
>>>>When I enter the following string in the shortcut target:
>>>>"C:\PROGRAM FILES\DEVSTUDIO\VFP\VFP.EXE -CC:\PROGRAM FILES\DEVSTUDIO\VFP\CUSTFILE.CFG"
>>>>As I expected, I am not permitted to save it because the switch is not part of the pathname and therefore makes the pathname invalid.
>>>>
>>>>The simple and obvious solution would be to remove VFP from it's present location and re-install it in it's own folder off the root directory. That way I wouldn't have to deal with nasty long folder names or folder names containing spaces. On the other hand, I feel there must be a solution to this. Does anyone have an idea?
>>>>
>>>>James McIlwrath
>>>
>>>
>>>Not sure but you can try one thing..
>>>
>>>Win 95 allows long file/folder names, when you go to msdos prompt..
>>>
>>>it shows the name in 8 char.. i.e. for Program Files it will show you something like progra~1..
>>>
>>>Take the exact path what it is showing you in Dos and then try it..
>>
>>Vinod,
>>
>>Your first suggestion worked perfectly. I simply replaced the folder name "Program Files" with "Progra~1 and VFP was able to find the custom configuration file. The new target string is now similar to the following:
>>"C:\PROGRA~1\DEVSTUDIO\VFP\VFP.EXE" -C":\PROGRA~1\DEVSTUDIO\VFP\CUSTFILE.CFG"
>>
>>Thank you very much and thanks to everyone else who responded.
>>
>>James McIlwrath
>>Datasmith Custom Software
>>Mississauga, ON
>>Canada
>
>you are welcome from all of us..