>>Thanks, I implemented a similar approach and all is well.
>>
>>>If you're setting your paths at startup, convert them to absolute at that point... like this:
>>>
Do addpath With 'libs'
>>> Do addpath With 'frx'
>>> Do addpath With 'forms'
>>> Do addpath With 'tools'
>>> Do addpath With 'stuff'
>>>...
>>>
>>>Proc addpath
>>> Lparam cPath
>>> Try
>>> cPath=FullPath(Addbs(cPath))
>>>
>>> If Directory(cPath)
>>> If Atc(cPath+',', Set('path')+',')=0
>>> cPath=Set('path')+','+cPath
>>> Set Path To (cPath)
>>> Endif
>>> Endif
>>> Catch To oEx
>>> Assert .F. Message oEx.Message
>>> Endtry
>>>
>Naomi,
>Hi,
>
>Forgive me, but would you be able to explain what you call a absolute path and what you call a relative path?
>
>so e.g. curdir() = "D:\Myapplication"
>
>is than
>
>"D:\MyApplication\Code" an absolute path
>
>and
>
>"\Code" a relative path ?
>
>I am a little bit puzzled
>
>Thanks for replying.
>
>Koen
>
>Is "D:\MyApplication\Code
Koen,
PDMFJI;
just like on old DOS times
absolute path
c:\dir1\dir2\dirn
or
\\Server\dir1\dir2\dirn
reative path
dir1
this means relative to the current path on current drive (the one you got with CD) directory named dir1
or
..
on level down from current
or
..\..\dir2
two levels down from current, then up to dir2
or
.\Dirx
relative to the current path on current drive up to dir Dirx
or
C:dir1
on drive C:, relative to the current path on C: up to directory dir1
or X:..\..\Dir2
on Drive X: two levels down relative to the current path on X: then up to Dir2
or
\User
relative to the current Drive / Server root, directory User
or
myfile.ext
relative to the current path a file in this path.
IOW
absolute is simply fully qualified from Drive/Server up to the final directory or file, while anything else is relative to something.
HTH
Agnes
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]