>>>>Is the dir that the executable was started from automatically the default dir if there's no config.fpw?
>>>>
>>>>If not, is there a way to determine what dir the exe was started from?
>>>>
>>>>Can you set the properties found in config.fpw, such as setting the temp file dir from within the app rather than the config.fpw?
>>>>
>>>>Is there some way to get CD, MD, RD to work with dirs that have spaces in their names?
>>>>
>>>>I think that's it for now. :)
>>>>
>>>>Thanks,
>>>>
>>>>-Michelle
>>>
>>>It can be done pretty simple:
>>>

>>>***Main.Prg
>>>oApp=CreateObject("clApp")
>>>oApp.startdir=SYS(5)+CURDIR()  && and use it throughout the application
>>>*****

Ed,

I've had problems using SYS(5) in some network environments with UNCs that aren't mapped,  I've found that FULLPATH(CURDIR()) works more reliably, especially with NetWare and some of Novell's Client32 implementations.

>>>RETURN
>>>
>>>DEFINE Class clApp As Custom
>>> .startdir=""
>>> **** other properties
>>>ENDDEFINE
>>>

>>
>>So I'm guessing the first answer is no, it isn't automatic. :)
>>
>>But if I can get it from "SYS(5)+CURDIR()", that's easy enough to do.
>>
>>Thanks,
>>
>>-Michelle
>
>It's automatic, but why take chances :), real application is so big and VFP itself is so intricated that some small property may have sense.