Hi !
I often map drives over a network (VPN) or map drives over a DSL
connection; a problem I often have is when the drive I am connected
to where a random file resides is not available or the ping response to it is way to long . .
What usually happens is my software would hang with no error display.
Is there any solution that could report the drive as unavailable sooner.
Although I trap the error with a error routine the process
before the operating system reports none availability is drawn out.
Is their anyway to trap the none availability of a drive sooner??
This is how I connect to the drive (sample random file):-
ON ERROR GOTO ERR_R:
OPEN"\\10.0.0.99\BACKUP\PROGRAMS\TEST.XXX" FOR RANDOM ACCESS READ WRITE SHARED AS #1 LEN=256
FIELD#1,256 AS T$
LSET T$="TSET XXX end"
PUT#1,1
GET#1,1
CLS
PRINT T$
CLOSE
END
ERR_R:
IF ERR=75 THEN PRINT”DRIVE DOWN ! ! ! “ RESUME (TO SUB WHICH WILL HANDLE THE ERROR”
Thanks in Advance
BASit
------------------
I often map drives over a network (VPN) or map drives over a DSL
connection; a problem I often have is when the drive I am connected
to where a random file resides is not available or the ping response to it is way to long . .
What usually happens is my software would hang with no error display.
Is there any solution that could report the drive as unavailable sooner.
Although I trap the error with a error routine the process
before the operating system reports none availability is drawn out.
Is their anyway to trap the none availability of a drive sooner??
This is how I connect to the drive (sample random file):-
ON ERROR GOTO ERR_R:
OPEN"\\10.0.0.99\BACKUP\PROGRAMS\TEST.XXX" FOR RANDOM ACCESS READ WRITE SHARED AS #1 LEN=256
FIELD#1,256 AS T$
LSET T$="TSET XXX end"
PUT#1,1
GET#1,1
CLS
PRINT T$
CLOSE
END
ERR_R:
IF ERR=75 THEN PRINT”DRIVE DOWN ! ! ! “ RESUME (TO SUB WHICH WILL HANDLE THE ERROR”
Thanks in Advance
BASit
------------------
Comment