Access mounted volumes on Windows from LC?

[Ben Rubinstein]

Hi Roger,

Thanks for your swift reply. Unfortunately this is using 6.7.7 (on Mac, 
building a standalone to run on Windows). Did you notice a regresssion?

TIA,

Ben

On 30/06/2016 14:50, Roger Eller wrote:
> UNC was broken in 6.6.4 to 6.7.1  (I reported the bug when my apps began to
> fail).  UNC was repaired in 6.7.5 and higher.
>
> ~Roger
>
>
> On Thu, Jun 30, 2016 at 9:37 AM, Ben Rubinstein <benr_mc at cogapp.com> wrote:
>
>> I spoke too soon.
>>
>> With the volume mounted, accessing it by drive letter works (so I assume
>> that this isn't a permissions problem); but using the UNC fails.
>>
>> If I use "answer folder" I get the path with drive letter, e.g.
>>         Z:/Docs/Invoices
>>
>> setting the defaultFolder to this path has the expected effect, using
>> "there is a folder..." on this path returns true, etc.
>>
>> But if I use the "UNC" version of path:
>>         //server/volume/Docs/Invoices
>>
>> then setting the defaultFolder returns "can't open directory", using
>> "there is a folder..." return false.
>>
>> Reversing the slashes makes no difference.
>>
>> SysError returns either 2 or 3 - seemingly randomly. Apparently
>>         2 = ERROR_FILE_NOT_FOUND
>>         3 = ERROR_PATH_NOT_FOUND
>>
>> This is on Windows Server 2008 R2 Enterprise.
>>
>> Previous answers suggested that some people have succeeded in accessing
>> directories using UNC paths. Can you share how you've done this?
>>
>> Many thanks,
>>
>> Ben
>>
>>
>> On 29/06/2016 17:07, Ben Rubinstein wrote:
>>
>>> It wasn't a mistyped path.... but it was my making a mistake! In my lack
>>> of
>>> Windows knowledge, I thought that the volume was mounted - but actually
>>> that
>>> was a server that was 'accessible', but with none of it's volume's
>>> mounted.
>>>
>>> Thanks to everyone for their assistance.
>>>
>>> Ben
>>>
>>> On 22/06/2016 17:02, Richard Gaskin wrote:
>>>
>>>> Mark Talluto wrote:
>>>>
>>>> The first thing to check is permission access to that folder.
>>>>> Have your program do a sample write to that location and get
>>>>> the results.
>>>>>
>>>>
>>>> That's too smart.  For me that's the second thing I do, but when I do in
>>>> addition to checking the result I also include a call to the sysError
>>>> function
>>>> so I can learn what the OS might be telling me.
>>>>
>>>> The first thing I do is assume I mistyped the path, so I'll run
>>>> something like
>>>> this in the Message Box to double-check it:
>>>>
>>>>   answer file "Select your file:"; put it
>>>>