>>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
>>
>>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?
>
>Hi James,
>I've seen this with specifing a shortcut to include a configuration file with my 2.6 apps. I dont know why this happens, but I know how to make it work in my environment. If the standard string C:\VFP\VFP.EXE -CC:\VFP\CUSTFILE.CFG doesnt work, then it will usually accept "C:\VFP\VFP.EXE"-CC:\VFP\CUSTFILE.CFG for me. Notice there is no space after the second quote mark and before the -C switch. Another note... I figured this out long way and my command strings are always in all lowercase. Why that might matter I dont know but something to try. HTH
>=D) Rox
>>
>>James McIlwrath

Also, you might try looking as the directory listing and look up the 8 character equivalent to the long directory names (ie.: PROGRAM FILES = PROGRA~1) That may also help.

HTH