>>> The VFP diskspace() function only works fine for drive letters.
>>
>>Since when? I have quite a few VFP6 apps still running that use UNC names just fine with DISKSPACE().
>
>Fred, thanks for correcting me!
>
>Diskspace() indeed gives results on UNC names. It was another drawback that forced me to write an alternative routine. On very large drives (either network or local) it returns the result in scientific notation. E.g. 1,158E+11 instead of 115818102784. This result can, of course, be used in displays and comparisons, but it is only an approximation of the real value. There's also a remark about it in the helptext.
>In many situations this drawback is of only minor importance. In my situation it is important, however.
>
>I'll correct my documentation of the alternative function immediately. ;)

No problem. I round my results off to the nearest 1/10 of a GB anyways. Works fine on our 1.5 TB (Terra Byte) server.