Reply from Excellin on May 27 at 10:33 AM Does anyone else experience this forum refreshing when you're providing a response, causing you to lose all the text you've written?
While you can ping a server, I didn't think that you could do that for a directory.
I know what you mean by Windows taking its time to check on a directory.
If you know of a file in the directory and can check, I believe that the results may be faster than if you're checking to see if the diretory itself exists. Try doing something like this:
Public Function FileExists(fname$) As Boolean
On Error GoTo ErrHandler ' in case of invalid path
If Dir(fname) <> "" Then
FileExists = True
Else: FileExists = False
End If
Exit Function
ErrHandler:
Err.Clear
FileExists = False
End Function
| | | ---------------Original Message---------------
From: ladyjade8
Sent: Friday, May 25, 2012 11:02 AM
Subject: Fastest Response to Check if a Network Path is Available
I have tried DirExists (path) and FileExists(path) and fso objects.
They all work great when the path is available. My problem is in when the application can't access the path.
Have app running on a touchscreen PC running windows XP embedded POS (Wepos) OS.
On a timer event it calls out to a server to see if drive is available to be written to. When it is not there is a long "not responding" period.
Does anyone know of a process that will return a failed response quicker or has the ability to include a timeout time.
Thanks for your time. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
No comments:
Post a Comment