>In light of or more of the recent threads in this area, here's a little something from the "Advisor Tips" section of FPA. As a side note, I find it interesting that Steve Sawyer is no longer the editor of this column.
>
>The title of this gem is "Determine if a Drive Exists". Without getting into any of the text, it has the following RETURN:

RETURN (DISKSPACE(tcDrive) > 0)

where tcDrive is the drive in question.
>
>Only one problem...under NT you get a nasty error dialog if SetErrorMode() isn't properly called (and later restored to it's original state) to disable it.
>
>Now if you're going to be mucking about with API anyway, then...

DECLARE INTEGER GetLogicalDrives IN Win32API
>RETURN BITTEST(GetLogicalDrives(), ASC(UPPER(tcDrive)) - 65)

>

And quickly, too! Even if SetErrorMode() is properly set to 1 so that the Critical Error is passed through to VFP to handle rather than firing up NT's A/R/I messagebox, it takes significant time to either read the drive by bringing it up to speed and reading the free space, or to time out because there's no disk present. Nice catch here, George - faster, cleaner, and OS insensitive!

Ever think about working as a tech editor? < g >

>gets the job done very cleanly.
>
>Back in the January, 2000 issue, while Steve was still the Contributing Editor, there was a tip that synchronized the VFP _DBLCLICK system variable with the setting the user had established in the Control Panel:

DECLARE INTEGER GetDoubleClickTime IN Win32API
>_DBLCLICK = GetDoubleClickTime() / 1000

I'd hate to say that the quality of the tips seems to have declined...but the quality of the tips seems to have declined, at least as far as the API and underlying testing of a tip to make sure it worked consistently on a cross-platform basis...