Frank Ramsey wrote in a message to Tony White:
 TW> Immediately after this upgrade occured, we started having 
 TW> problems with file corruptions with large Excel 
 TW> spreadsheets.  Excel returns an "Unable to read file" 
 TW> error message while loading.  This is not happening on 
 FR> Is compression enabled on the Netware volumes?  Is there enough
 FR> free space on the volumes to decompress the files?  Have you tried
 FR> copying the files to the local hard drive and then opening into
 FR> Excel from the local drive?  I'm trying to figure out if the
 FR> problem is the network or the files.
I'll have to check on compression -- I don't remember as I sit here whether 
we enabled it or not.  Saving the files to the local drive works fine.  
Saving them to the network is a crapshoot.  Copying a file that won't open 
from the network to the local drive doesn't work -- the file still won't 
en.
Microsoft's KB has some very interesting things to say about Excel 
corruption.  You ought to check it out sometime.  Basically, it says that 
Excel does not save files in a linear manner, but "staggered".  Microsoft's 
KB suggests "troubleshooting" (not solving) by disabling a number of features 
which makes me wonder whether or not Excel bypasses C32 and talks directly to 
NDIS...
 
Regards,
-TWhite 
--- timEd 1.10
---------------