>>>
>>>set defa to (gcWhereAmI)
>>>
>>>This way the app doesn't give a damn for its location - it knows where it is, uses it as the default path and all the relative paths follow from there.
>>
>>Yeah, I do this as well. He (Evan) was having difficulty defining a UNC path to his DBC and tables which are on a network drive while the APP is installed on local drive.
>
>Ah, that's another geography. Should take the initial path from any file which surely resides at the target directory, remember it and explicitly Set Default to it. The rest should be the same. AFAI remember his problem (can't see previous messages in UT Nav), he wanted to avoid hardcoding the path. If he can make sure his app is launched in proper folder, he could just
>
>Set Default to (curdir())
>
>I think that, lacking the Set Default, relative paths get lost on the way, or am I wrong? If I am, what caused his problem then?

You are correct. Relative paths definitely depend on where you are as defined by the set default. I keep my path in an individual user table on the user's workstation (DB is on a server, the app is installed to workstation) but in UNC format so I do not have to depend on absolute drive mapping. If the app can not find DBC based on the stored UNC path, I launch a form for the user to use to locate the data with a getfile() option.