Yep, but if I present my user with a value that differs from what Explorer tells the user, then he might decide to give me a call.
>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. ;)
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
