I also normally do not do a set path. I do you the same methodology to do a SET DEFAULT.

-myron kirby-
myronk@flash.net
-----------------------------------------
>>>Mr Kirby
>>>i, sorry but i dont undertand that you traing to explain me .. let me see
>>>you say that i have to read the unit from the win.ini of the user?
>>>when you say that i could
>>>
>>>> SET PATH TO (oApp.PathTemp)
>>>tyhis is the way to read the unit of the user? ( i dont know what is > oApp.PathTemp ( any event in VFP)
>>>>
>>> USE (oApp.PathTemp + [])
>>>is this the way to acces a table whatever unit the user has?
>>>
>>>i'm sorry again but you know
>>> i think that my knowledege in vfp 5.0 is not too big like yours
>>>
>>>thanks again
>>>A.M.G
>>Augusto,
>>To set paths for your app, I think it's easiest to do it in config.fpw (and editable for multiuser environments w/o recompiling or extra code). Use relative paths rather than fixed so the app dir could be moved w/o need to change it.
>>

>>*cDrive:\..\AppDir
>>*cDrive:\..\AppDir\data
>>*cDrive:\..\AppDir\report
>>*Config.fpw
>>path=data;report;
>>

>>Anyway if you want to do it code then you could use :
>>

>>set path to data;report       && Again relative paths
>>* set path to (home()+"data;"+home()+"tools") && Alternative way
>>

>>Cetin
>
>With invention of dbc file and DE objects the necessity of SET PATH command gone away, i.e. it's redundant command which just makes waters muddier.

----------------------------------
-myron kirby (mkirby2000@gmail.com)-