TW> I'll have to check on compression -- I don't remember as I 
 TW> sit here whether we enabled it or not.  Saving the files 
 TW> to the local drive works fine.  Saving them to the network 
 TW> is a crapshoot.  Copying a file that won't open from the 
 TW> network to the local drive doesn't work -- the file still won't open.
I'd say you got serious network problems.  Look for every updated driver you 
can find.  And apply the latest patch kits.  Don't believe this is the 
problem, however, better safe than sorry.  
The only problems we've had here concerning Excel and saving to a net drive 
is occasionally, the client cannot save anywhere.  Seems to happen when the 
net drive runs out of space.  Once it happens, doesn't matter where you try 
to save, net or local.  Doesn't work.
Other than this, Excel files are saved and reloaded all the time here.
 TW> Microsoft's KB has some very interesting things to say 
 TW> about Excel corruption.  You ought to check it out 
 TW> sometime.  Basically, it says that Excel does not save 
 TW> files in a linear manner, but "staggered".  Microsoft's KB 
 TW> suggests "troubleshooting" (not solving) by disabling a 
 TW> number of features which makes me wonder whether or not 
 TW> Excel bypasses C32 and talks directly to NDIS...
We've seen some real interesting things with many Microsoft products.  IBM 
reports that loading Windows from the network results in Windows loading from 
the end of files to the beginning.  You can imagine how useful caching 
becomes when trying to load from end to beginning.
framsey@goodyear.com; CIS 71631,1032 - CNE, CNA-4, PE
--- EZPoint V2.2
---------------