SNIP>
>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.

On the other hand, Peter, when I buy a 40GB HD or a 160GB HD those number turn out to be approximate too (I'd say). Yes, the 40"GB" drive indeed has 40,000,000,000 bytes available and the 160 "GB" has 160,000,000,000 bytes, but neither of those actually complies to the 'definition' of GB.

cheers

>
>I'll correct my documentation of the alternative function immediately. ;)