Thank you for the fopen idea. I am not using share and I don't know if
the drive is mapped or UNC. After playing around with fopen though, I
discovered that the error is an OS/network error. What I wanted to do
was, if the network drive failed, then fp would default to the local
drive,
I got these too. I told him to fuck off.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
On Thu, 22 Oct 2015, at 05:19 PM, Kurt Wendt wrote:
> I tried sending this e-mail, but, it didn't go thru - probably caught by
> Ed's Spam filters (funny - since this is essentially about SPAM). So -
I'm not sure FPD or Windows see a NAS any differently than any shared
drive from any kind of source...another Windows machine, a Linux box, or
a Windows server.
Mike Copeland
Lew Schwartz wrote:
The earlier idea on this thread of trapping the error with an on error
routine and/or a more
Subtle as ever :-)
John Weller
07976 393632
01380 723235
Sent from my iPhone
>
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list:
The earlier idea on this thread of trapping the error with an on error
routine and/or a more robust analysis where the fopen() error number is
captured might work. I haven't written code like this for years, but I
don't remember network drives being a problem. I never worked with NAS
drives,
5 matches
Mail list logo