=> -----Original Message----- => From: [EMAIL PROTECTED] => [mailto:[EMAIL PROTECTED] On Behalf Of Malcolm Greene => Sent: Tuesday, October 03, 2006 15:43 => To: [email protected] => Subject: Quickly determining a UNC path is bad? => => Any suggestions for quickly determining that a UNC path is bad? => => Example: => => ? FILE( '\\bad\bad.txt' ) => => It takes 10-15 seconds for VFP to determine a UNC path is => invalid on my workstation (XP Pro SP 2). => => Is there an alternative technique for quickly validating a UNC path? => => Thanks, => Malcolm
That's not a bad time; sometimes it takes me 45 seconds. If you are on a network, the problem is due to requests for resources timing out because there is no availability. It is the nature of the OS. If your users are choosing the bad name, it is their fault. If your software is choosing, it needs to be better educated. HALinNY _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
