What is the correct syntax to set the default directory in FP 2.6? In
the comand window it is:
"set default to c:\mydir" - but this is not working in the config
I don't think you can set default in CONFIG.FPx, but by definition program'sQuote:>What is the correct syntax to set the default directory in FP 2.6? In
>the comand window it is:
> "set default to c:\mydir" - but this is not working in the config
[ When replying, remove *'s from address ]
Alexandre Pechtchanski, Systems Manager, RUH, NY
In FPW or FPD help look for "Configuring FoxPro" - "Startup Files" and
"Special CONFIG.FPW Settings".
DEFAULT = c:\mydir
hoping this helps
Christian Desbourse (Belgium)
DEFAULT=<full path, no quotes>
I had this in a VFP CONFIG file, but I am sure I have used this in 2.6
as well...hope this helps...
The online help under CONFIG.FPW talks more about configuration
Are you going to distribute your app to other users on your network?
If so, you may not want to use such in the config.fpw.
(There are better/other ways.)
In my experience ninety percent of the time the runtime version ofQuote:>Tip:
>Make sure FoxPro is reading the correct CONFIG.FP. It is a very common
>programmer error to be reading the wrong configuration file, i.e. one
>other than the one intended. If FoxPro can't find a configuration file
>it will search the DOS path and grab the first one it finds and this
>could be anywhere on a network.
Target: "O:\SWHLIVE1\SWHMAINW.EXE -CO:\DOSPROG\CONFIG.FPW"
The application itself then checks key SYS values to make sure that it
was setup properly & refuses to run if it wasn't.
On a more philisophical point though, I would be a little wary of using
CONFIG.FPW to "Set Default To". In a network environment that might
prove to be a little restrictive.
You are quite correct.Quote:
> Make sure FoxPro is reading the correct CONFIG.FP. It is a very common
> programmer error to be reading the wrong configuration file, i.e. one
> other than the one intended. If FoxPro can't find a configuration file
> it will search the DOS path and grab the first one it finds and this
> could be anywhere on a network.
> You can discover which CONFIG.FP FoxPro is utilizing by calling the
> SYS(2019) function. Here are three commands that you can use from the
> command window (or in a program) that are very useful when trying to
> debug in these situations:
> WAIT WIND SYS(2019)
> MODI COMM SYS(2019)
Has anyone ever seen an error message of
"Default Config File not Found"?
A user of my system in another state is getting that error about the time
in the program when a RUN/N is being performed (but might be just
before it, when I'm doing some DELETE FILEs).
I don't think the program that is being called (SAS) is causing the
problem, but I'm hoping for a clue before I fly cross-country tomorrow.
E-mail would be appreciated,
Systems Project Leader, CANDA Systems
G.D. Searle & Co.
Can you imagine a world where there are no hypothetical questions?