> >Checking available space is precaution measure and few more MB will not hurt. IMHO, this horse (thread) is dead:).
'A few more MB' is not the issue with our environment - VFP tables are very compressible, and may approach the 2:1 ratio level with both FAT/DriveSpace and NetWare 4.x's compression modes. means our ceiling estimates approach being twice what they might need to be. IOW, if you figure that you've enough space, great, but even if your ceiling estimate fails to be met by 15-20% when based on physical space available, your data might fit.
Or worse, if DISKSPACE() is based on the compressed data space available estimate, and your data doesn't compress well (ie you embed lots of binary stuff in memo/character fields) you might need far more space than DISKSPACE() thinks is available, since you don't really know what assumptions were made in estimating the ratio of compressed vs non-compressed storage. Since our tables tend to be large, any estimates of space saving based on lower slack space allocation from suballocation for small target files would probably be very wrong.
