Accessing files on a local network file server - BEST PRACTICE?

Paul Dupuis paul at
Fri Sep 25 18:24:05 EDT 2020

Thanks Bob,

Yes, the error messages you get on a failed file open are pretty generic.

I am thinking that whether Mac or Win, the key is to check for whether 
there is a folder:

/volumes/mountpoint/ (osx)
//server/mountpoint/ (win)

For a given path tPath, I can tell if it is a windows server bu looking 
at the 1st two characters of tPath and if they are // then I can try t 
pull off //server/mountpoint and test for a folder by that name exists.

However, on OSX,

/volumes/mountpoint/ looks just like any local path.

On 9/25/2020 6:12 PM, Bob Sneidar via use-livecode wrote:
> QUALIFIER: this is in Livecode on a Mac. Mac mount points work differently than Windows. However using the form /volumes/mountpoint/folderpath/filename I get the simple error “Can’t open that file.” No detail about WHY I cannot open it. I can see how it would be helpful if the result contained “path not accessible”, “write access denied”, “file already exists” etc.
> Bob S
> On Sep 25, 2020, at 2:28 PM, Bob Sneidar via use-livecode <use-livecode at<mailto:use-livecode at>> wrote:
> OK using your convention I cannot even open a file with the server mounted and an actual file that DOES exist! (//servername/mountpoint/pathtofile/filename)
> Bob S
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list