>>Do you mean that the standard \\server\volume syntax is giving you problems? If so, I've run into similar things trying to map drives on a Novell system when trying to map drives using both VFP and the Windows Script Host. If the server is not part of the same branch of the tree (I'm not sure exactly about the terminology here, BTW), it wouldn't map. An example, using our net as an example would be using \\SNnn\MAIN where "nn" is the plant number. In this case, it would map to any of the five servers with our particular group, but woudn't work outside of it.
>>
>
>Yes, especially when we ShellExec() Winzip as it defaults to the Windows Terminal Services temp (or tmp) setting when you use UNC paths. Even more so because aside from the Citrix environment; they have a Web Server where they use published Web ICAs and run the app from there.
>
>>The workaround was to first map a drive using the Windows Explorer, then retrieving the name using either the WSH or using the WNetGetConnection() API call and using that where necessary.
>
>Their IT allowed us to map a drive and we have to 'hard-code' the path in our Settings.dbf where we store application data such as file locations. This helped a lot.
>
>On the second topic about clustering where the dataset server will have an identical server; which I assume will become active if the other dataserver fails. I've heard of cluster-aware apps and Windows clustering APIs. Is it necessary for VFP to be cluster-aware?

I don't really feel qualified to answer this question, Ramil. My hunch would be that it isn't based on my overall knowledge of Windows and how applications inter-act with it. However, if someone else here tells you otherwise, I recommend that you take their word for it.