>>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,
>
>If you use UNCs, they aren't going to start with :, but instead, will be in the form \\. Before prefixing with a drive letter, you'd best make certain that the path or path string does not begin with '\\', since SYS(5) in particular is known to return a funky value of '\:'.

Ed,
The above was an example of what I do at the moment. I am looking for info on UNC and other alternatives. I want to get away from the way I do things in 2.6 and when I rewrite them in VFP, do them similar to the VFP apps I do at the moment (which is the second example) but possibly even better than the way I now do them. I'm beginning to think UNC may not be better though - you still need the same server/volume structure.

Nigel B Coates
NBC Software Services
Dublin, Ireland.
eMail: Nigel.Coates@NBCSoftware.com