>I would like to add UNC functionality (or something similar) to my systems and also update some documentation I am working on regarding programming concepts. I do not know enough about UNC and would like some peoples views. At the moment, I use two different approaches; in 2.6, I do the following at the start of the main program:-
>
>

>lcCustRoot=lcMainDrive+":\customer\"
>lcCustPath=lcCustRoot+lcCustCode+'\'     && lcCustCode = customer code
>lcCustFile=lcCustPath+lcCustCode+".dbf"  && customer database
>

>
>In VFP I do similar but place items in a text (ini) file and use low level file handling to pick out the bits I need. Example: "CustomerRoot=:\customer\". I would like to know what other people do and how flexible those different approaches are. TIA,
Nigel,
UNC is much like mapping but you must use FULL UNC path instead of relative subdir addressing.

path=data;report && Wrong
path=\\server\...\data;\\server\..\report && True

and you should include UNC path in shortcut for config.fpw (Target: \\server\...\app\app.exe -C\\server\...\app\config.fpw).
Cetin