Malcolm,
I wonder if the API for FindFirstFile works as fast as File()
DECLARE INTEGER FindFirstFile IN kernel32;
STRING lpFileName,;
STRING @ lpFindFileData
lpFileName="\\server\temp.txt"
lpFindFileData=Replicate(Chr(0),300)
*
? FindFirstFile(lpFilename, @lpFindFileData)
Unfortunately I don't know the length of the structure of type
WIN32_FIND_DATA off hand (I'm just off to bed) so I've put in 300 as a
guess.
Dave Crozier
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Malcolm Greene
Sent: 03 October 2006 20: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
[excessive quoting removed by server]
_______________________________________________
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.
