This is a common problem when the network is Windows 2000, the problem is compounded when the server is also running Netware- Novel at the same time. The problem stems from the extream latency time of the network, which could be made even more of a problem when the application is on the network rather than the local PC.
The user must allow extra time for any Excel action and not save until Excel is done doing what-ever. If you have a network collision due to the lattency issue you will get this message. Micro Soft does not have a fix for this, but thinks if the network is a Windows 2000 only the problem will be minimized. You will not have this problem if each local PC has its own copy of Office-Excel installed on its Local Drive.
When this happens the backup file is stored on the local PC's default folder for the working copy of Excel, but it is hidden. To find the backup copy of the file, have the user write down the backup file name it will be something like: EO00234X4. On the Open file utility of Excel switch the file view to all files, then look for the backup file, open it and re-name it all the users work should be there. JSW
Win2000 and NT have the same core. The problem is other clients who may be running Novel servers it seems?
Seeing the temp file problem is in Excel. The "Open" file is set to show Excel WorkBooks "xls" the temp file is not saved with the "xls" extention. So many users have difficulty finding the file even if they know the name. The other problem is Excel may not put the temp file in the users working directory, so you may need to do a little hunting to find it in some configurations. JSW