10-01-2024 04:29 PM
Hello,
I have a customer with a server that I am trying to save some files to.
The path is \\\\AST\home\public.
I am thinking the 4 \ is giving me problems. I was doing some research and server paths usually start with just 2 \ (i.e. \\AST\home\public)
Any suggestions on how to handle this? Do I just remove to 2 \ or is there a more elegant way?
Thanks
10-01-2024 10:52 PM
@ASTDan wrote:
Hello,
I have a customer with a server that I am trying to save some files to.
The path is \\\\AST\home\public.
I am thinking the 4 \ is giving me problems. I was doing some research and server paths usually start with just 2 \ (i.e. \\AST\home\public)
Any suggestions on how to handle this? Do I just remove to 2 \ or is there a more elegant way?
Thanks
It is weird that it contains four "\", my search also resulted in "\\" only and not four.
10-02-2024 01:25 AM
What is the OS of the server?
Is this a path datatype or a string?
If this is a plain string and is set to \-code display, "\\a\b\c" would show as "\\\\a\\b\\c", also duplicating the other ones. Not quite the same.
How are you communicating with the server? Is this just a network shared drive?
In what sense is it "giving you problems"? (error messages, etc.) What have you tried? What problems did you get when using only two at the beginning?
10-02-2024 01:37 AM - edited 10-02-2024 01:44 AM
Could it be that the other backslashes in that path are actually double and you missed that? In that case your customer simply copy-pasted the path from a C source or something else using \ escaping. A UNC server name does look like \\\\server\\share\\path in \ escaped form as used in C code.
LabVIEW strings or paths don’t use that unless you set the string explicitly into \~Code display mode.
There is another path prefix in Windows that is \\?\ or \\.\ which indicate to Windows to skip path length limitation for file respectively device paths but that is a very special kernel detail.
10-02-2024 09:39 AM