Barbara -

Thanks for the reply. I got my setup working, but in a wierd way. In order to get the statements to execute, I had to call a program from my config file. So my config file only has one line -- "COMMAND = DO CONFIGMB". That works fine; but if I put the identical statements in the config.fpw file, they don't work!

Other wierdness--when I double click on a fpw file (after associating VFP.exe with that extension), I get the message "program.prg" not found.

I'll check out the foxuser.dbf thread.

-Mark

>Mark, I DID find the problem, and it was really weird. Everything worked on one computer, but not on the other. The difference wasn't in VFP at all, but in the AUTOEXEC.BAT file. It turned out I needed to add "Windows\system" to my path. I decided that VFP5 needed access to some library that wasn't available at load time. Anyway, with this minor addition everything is fine. Took several hours of re-installing and comparing setups between the 2 computers before I discovered it, though.
>
>Also, have you looked at the Foxuser.dbf thread from this week? I saw that deleting that solved several strange problems for Rob Keith as well as for me.
>
>HTH
>Barbara
>
>>Barbara-
>>
>>Did you ever get your config.fpw problems sorted out? If so, what did you do to solve them? I am having some problems with this file as well and found this thread while searching. Thanks.
>>
>>-Mark
>>
>>>>>>I can't get VFP to accept the -C prompt for any config file. It will read the CONFIG.FPW in the startup directory, but won't accept any other file name or path. I'd like to have different config files for development and run-time, but can't get it setup.
>>>>>>
>>>>>>Present syntax:
>>>>>>
>>>>>>c:\vfp50\vfp.exe -Cc:\mydir\config.xxx
>>>>>>
>>>>>>ONLY works for config.fpw!
>>>>>>
>>>>>>TIA
>>>>>>Barbara
>>>>>
>>>>>
>>>>>Did you include a CONFIG.FPW in the project? There is a bug that if you have an inculded CONFIG.FPW, you can't override it.
>>>>>
>>>>>Craig
>>>>
>>>>Basically, not bug but feature, very deceptive one.
>>>
>>>Craig, I didn't include the CONFIG.FPW in the project (even went back and double checked). I even went to a brand new directory, where the only file was the PRG I used for my test EXE (see VFP5 EXE Problem thread) and wrote a new CONFIG file with a different extension. VFP simply said 'Cannot find Config file' and loaded its default values.
>>>
>>>Edward, I'm beginning to think that whether a bug is a feature (and vice versa) is a matter of what your program is doing at any given moment!
>>>
>>>Thanks,
>>>Barbara