Re: Accessing files on a local network file server - BEST PRACTICE?
The shell command "net use" should return a list of currently available
network volumes.
In LC:
put shell("net use")
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthworld.comhttp://www.FourthWorld.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
Well, at least you have a server to test it on. Thank you.
I am trying to resurrect a Windows 2003 Server VM and a Windows 7 VM
configured to have it's home directory on the server. I just got both to
run (finally) yesterday and just (at the end of teh day today) figured
out what the admin password was to the 2003 server.
Maybe by sometime next week, I'll be able to test some code.
On 9/25/2020 7:26 PM, Bob Sneidar via use-livecode wrote:
After a little experimenting it appears that open file does not create a new
file on OS X mount points! I can open a file that already exists but it will
not create a new file. You learn something new every day!
Bob S
On Sep 25, 2020, at 4:21 PM, Bob Sneidar via use-livecode
wrote:
Hmmm. Neither does open file for read…
Bob S
On Sep 25, 2020, at 4:20 PM, Bob Sneidar wrote:
Even worse, if the mount point is mounted it does not create the file.
Bob S
On Sep 25, 2020, at 4:18 PM, Bob Sneidar via use-livecode
wrote:
Unfortunately, if it fails no error is generated, and nothing is in the result
or the it variable.
Bob SW
On Sep 25, 2020, at 3:56 PM, Ralph DiMola via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
On my Mac this form works to a Win 10 smb share
put url ("file://volumes/shareName/folder/sub-folder/file.ext")
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
After a little experimenting it appears that open file does not create a new
file on OS X mount points! I can open a file that already exists but it will
not create a new file. You learn something new every day!
Bob S
> On Sep 25, 2020, at 4:21 PM, Bob Sneidar via use-livecode
> wrote:
>
> Hmmm. Neither does open file for read…
>
> Bob S
>
>
>> On Sep 25, 2020, at 4:20 PM, Bob Sneidar wrote:
>>
>> Even worse, if the mount point is mounted it does not create the file.
>>
>> Bob S
>>
>>
>>> On Sep 25, 2020, at 4:18 PM, Bob Sneidar via use-livecode
>>> wrote:
>>>
>>> Unfortunately, if it fails no error is generated, and nothing is in the
>>> result or the it variable.
>>>
>>> Bob SW
>>>
>>>
>>> On Sep 25, 2020, at 3:56 PM, Ralph DiMola via use-livecode
>>> mailto:use-livecode@lists.runrev.com>> wrote:
>>>
>>> On my Mac this form works to a Win 10 smb share
>>>
>>> put url ("file://volumes/shareName/folder/sub-folder/file.ext")
>>>
>>> Ralph DiMola
>>> IT Director
>>> Evergreen Information Services
>>> rdim...@evergreeninfo.net
>>>
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
Hmmm. Neither does open file for read…
Bob S
> On Sep 25, 2020, at 4:20 PM, Bob Sneidar wrote:
>
> Even worse, if the mount point is mounted it does not create the file.
>
> Bob S
>
>
>> On Sep 25, 2020, at 4:18 PM, Bob Sneidar via use-livecode
>> wrote:
>>
>> Unfortunately, if it fails no error is generated, and nothing is in the
>> result or the it variable.
>>
>> Bob SW
>>
>>
>> On Sep 25, 2020, at 3:56 PM, Ralph DiMola via use-livecode
>> mailto:use-livecode@lists.runrev.com>> wrote:
>>
>> On my Mac this form works to a Win 10 smb share
>>
>> put url ("file://volumes/shareName/folder/sub-folder/file.ext")
>>
>> Ralph DiMola
>> IT Director
>> Evergreen Information Services
>> rdim...@evergreeninfo.net
>>
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
Even worse, if the mount point is mounted it does not create the file.
Bob S
> On Sep 25, 2020, at 4:18 PM, Bob Sneidar via use-livecode
> wrote:
>
> Unfortunately, if it fails no error is generated, and nothing is in the
> result or the it variable.
>
> Bob SW
>
>
> On Sep 25, 2020, at 3:56 PM, Ralph DiMola via use-livecode
> mailto:use-livecode@lists.runrev.com>> wrote:
>
> On my Mac this form works to a Win 10 smb share
>
> put url ("file://volumes/shareName/folder/sub-folder/file.ext")
>
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
Unfortunately, if it fails no error is generated, and nothing is in the result
or the it variable.
Bob SW
On Sep 25, 2020, at 3:56 PM, Ralph DiMola via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
On my Mac this form works to a Win 10 smb share
put url ("file://volumes/shareName/folder/sub-folder/file.ext")
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
RE: Accessing files on a local network file server - BEST PRACTICE?
On my Mac this form works to a Win 10 smb share
put url ("file://volumes/shareName/folder/sub-folder/file.ext")
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
Paul Dupuis via use-livecode
Sent: Friday, September 25, 2020 6:24 PM
To: use-livecode@lists.runrev.com
Cc: Paul Dupuis
Subject: Re: Accessing files on a local network file server - BEST PRACTICE?
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)
or
//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
> mailto:use-livecode@lists.runrev.com>> 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@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
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) or //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 mailto:use-livecode@lists.runrev.com>> 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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
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 mailto:use-livecode@lists.runrev.com>> 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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
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 > On Sep 25, 2020, at 2:22 PM, Bob Sneidar via use-livecode > wrote: > > Have you tried opening the file then checking the result? > > Bob S > > >> On Sep 25, 2020, at 12:13 PM, Paul Dupuis via use-livecode >> wrote: >> >> On 9/25/2020 2:42 PM, J. Landman Gay via use-livecode wrote: >>> I know very little about Windows network addresses, but from the example >>> you gave, I'd check to see if (slash-delimited) item 1 of the path is a >>> single letter followed by a colon. >>> >> >> Thanks for thought. >> >> In a Windows server environment (i.e many corporation, government agencies, >> etc.), computer are often set so tat their specific "User" directories >> (Documents, Desktop, "Home", etc.) at on a server rather than local disk. So >> a path to a file called "somefile.txt" is a user's Documents folder looks >> like: >> >> //s1.somedomain.com/mountPoint//Documents/somefile.txt >> >> The question is, if you execute the line of LiveCode script: >> >> if there is a file >> "//s1.somedomain.com/mountPoint//Documents/somefile.txt" then >> -- true >> else >> -- false >> end if >> >> In the "true" case, the file is there, which means the server and network >> are both accessible. Yea! proceed with whatever. >> >> In the "false" case, you do not know whether the FILE is missing OR the >> NETWORK is disconnected or the SERVER is down. >> >> It is in the "false" case that I am looking for approaches (if there are >> any) to tell the difference between >> 1) the file is missing >> and >> 2) the network or server is down. >> >> Bernard has a suggestion of keeping an invisible file. Being hidden, it is >> unlike that it could be removed by intent or accident and so, if the file I >> am looking for "somefile.txt" does not exists, I could test for the hidden >> file. If that exists, I know my file is missing and the server and network >> are still up. If the hidden file also does not exists, the server or network >> is "probably" down. >> >> I could probably improve on Bernard's suggestion by testing for: >> >> if there is a folder "//s1.somedomain.com/mountPoint/" then >> -- the server is up >> else >> -- the server or network is down OR or the user has been fired and their >> account delete! >> end if >> >> I was hoping someone out there had actually dealt with LiveCode working with >> files on a Windows network server and have a definite approach. Maybe >> testing for the user's folder is the definitive way OR the mountPoint folder >> may be even better? >> >> -- Paul >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
Have you tried opening the file then checking the result? Bob S > On Sep 25, 2020, at 12:13 PM, Paul Dupuis via use-livecode > wrote: > > On 9/25/2020 2:42 PM, J. Landman Gay via use-livecode wrote: >> I know very little about Windows network addresses, but from the example you >> gave, I'd check to see if (slash-delimited) item 1 of the path is a single >> letter followed by a colon. >> > > Thanks for thought. > > In a Windows server environment (i.e many corporation, government agencies, > etc.), computer are often set so tat their specific "User" directories > (Documents, Desktop, "Home", etc.) at on a server rather than local disk. So > a path to a file called "somefile.txt" is a user's Documents folder looks > like: > > //s1.somedomain.com/mountPoint//Documents/somefile.txt > > The question is, if you execute the line of LiveCode script: > > if there is a file > "//s1.somedomain.com/mountPoint//Documents/somefile.txt" then > -- true > else > -- false > end if > > In the "true" case, the file is there, which means the server and network are > both accessible. Yea! proceed with whatever. > > In the "false" case, you do not know whether the FILE is missing OR the > NETWORK is disconnected or the SERVER is down. > > It is in the "false" case that I am looking for approaches (if there are any) > to tell the difference between > 1) the file is missing > and > 2) the network or server is down. > > Bernard has a suggestion of keeping an invisible file. Being hidden, it is > unlike that it could be removed by intent or accident and so, if the file I > am looking for "somefile.txt" does not exists, I could test for the hidden > file. If that exists, I know my file is missing and the server and network > are still up. If the hidden file also does not exists, the server or network > is "probably" down. > > I could probably improve on Bernard's suggestion by testing for: > > if there is a folder "//s1.somedomain.com/mountPoint/" then > -- the server is up > else > -- the server or network is down OR or the user has been fired and their > account delete! > end if > > I was hoping someone out there had actually dealt with LiveCode working with > files on a Windows network server and have a definite approach. Maybe testing > for the user's folder is the definitive way OR the mountPoint folder may be > even better? > > -- Paul > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
On 9/25/2020 2:42 PM, J. Landman Gay via use-livecode wrote: I know very little about Windows network addresses, but from the example you gave, I'd check to see if (slash-delimited) item 1 of the path is a single letter followed by a colon. Thanks for thought. In a Windows server environment (i.e many corporation, government agencies, etc.), computer are often set so tat their specific "User" directories (Documents, Desktop, "Home", etc.) at on a server rather than local disk. So a path to a file called "somefile.txt" is a user's Documents folder looks like: //s1.somedomain.com/mountPoint//Documents/somefile.txt The question is, if you execute the line of LiveCode script: if there is a file "//s1.somedomain.com/mountPoint//Documents/somefile.txt" then -- true else -- false end if In the "true" case, the file is there, which means the server and network are both accessible. Yea! proceed with whatever. In the "false" case, you do not know whether the FILE is missing OR the NETWORK is disconnected or the SERVER is down. It is in the "false" case that I am looking for approaches (if there are any) to tell the difference between 1) the file is missing and 2) the network or server is down. Bernard has a suggestion of keeping an invisible file. Being hidden, it is unlike that it could be removed by intent or accident and so, if the file I am looking for "somefile.txt" does not exists, I could test for the hidden file. If that exists, I know my file is missing and the server and network are still up. If the hidden file also does not exists, the server or network is "probably" down. I could probably improve on Bernard's suggestion by testing for: if there is a folder "//s1.somedomain.com/mountPoint/" then -- the server is up else -- the server or network is down OR or the user has been fired and their account delete! end if I was hoping someone out there had actually dealt with LiveCode working with files on a Windows network server and have a definite approach. Maybe testing for the user's folder is the definitive way OR the mountPoint folder may be even better? -- Paul ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
I know very little about Windows network addresses, but from the example you gave, I'd check to
see if (slash-delimited) item 1 of the path is a single letter followed by a colon.
On 9/24/20 3:53 PM, Paul Dupuis via use-livecode wrote:
This question may have an obvious answer, but I am brain dead today, so here
goes:
I have a app installed with some customers in a Windows network environment. They have all
their laptops set so that their Home directories are on a local network server.
So, where as on a local laptop, specialFolderPath("documents") might return
"C:/Users//Documents" as the path, for them specialFolderPath("documents") returns
something like "//s1.somedomain.com/mountPoint//Documents"
We save a number of folders and files in the user's Documents folder. In some cases, if the
file is not present (i.e. if there is a file tFile is false) we regenerate the file from a
default.
Sometime, the server is offline or the user is disconnected from the network.
What is a good way to differentiate between:
1) one of these files is not present so must be regenerated, i.e
if there is not a file (specialFolderPath("documents")) then
-- regenerate the file tFile at location specialFolderPath("documents")
Versus
2) The Server (//s1.somedomain.com/ is disconnected to down?
So that in case (1) , we regenerate the file and in case (2) we present a warning that the
server is disconnected or down?
Mu gut says this should be simple, but I just can not wrap my brain around it
today.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Accessing files on a local network file server - BEST PRACTICE?
>>
So that in case (1) , we regenerate the file and in case (2) we present
a warning that the server is disconnected or down?
<<
For (2) you could save an empty file (as a flag of availability) and set
it's attribute to hidden.
If the file is not there when you get the files, then the folder is
unavailable. Because it's a hidden file, users won't see it if they open
the folder using (most) other applications (Explorer only shows such files
if the 'show hidden' checkbox is ticked).
This file can then be filtered out based on file name when you get the
files of that folder to present to the user. It's just your internal check
for folder availability. I guess there are some "net use" commands that
would show which shares are available/unavailable, but it's a long time
since I did that kind of system admin.
To programmatically set a file attribute to hidden on Windows use the shell
command to issue this "attrib +h _ServerAvailable.txt"
Hope that helps.
On Thu, Sep 24, 2020 at 9:54 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
> This question may have an obvious answer, but I am brain dead today, so
> here goes:
>
> I have a app installed with some customers in a Windows network
> environment. They have all their laptops set so that their Home
> directories are on a local network server.
>
> So, where as on a local laptop, specialFolderPath("documents") might
> return "C:/Users//Documents" as the path, for them
> specialFolderPath("documents") returns something like
> "//s1.somedomain.com/mountPoint//Documents"
>
> We save a number of folders and files in the user's Documents folder. In
> some cases, if the file is not present (i.e. if there is a file tFile is
> false) we regenerate the file from a default.
>
> Sometime, the server is offline or the user is disconnected from the
> network.
>
> What is a good way to differentiate between:
>
> 1) one of these files is not present so must be regenerated, i.e
>
> if there is not a file (specialFolderPath("documents"))
> then
>-- regenerate the file tFile at location specialFolderPath("documents")
>
> Versus
>
> 2) The Server (//s1.somedomain.com/ is disconnected to down?
>
> So that in case (1) , we regenerate the file and in case (2) we present
> a warning that the server is disconnected or down?
>
> Mu gut says this should be simple, but I just can not wrap my brain
> around it today.
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
