+ 0 Votes Perhaps one of the settings in this KB article seanferd 4 years ago could use an adjustment. http://support.microsoft.com/kb/296264 Perhaps see this also for any hints it might offer: http://support.microsoft.com/kb/812937 The basic mechanism I imagine to be involved here is lazy writing to disk. There may be some difference as to how this occurs in 2k3 vs. 2k. This also had some info in it, although it is addressing a specific third-party product. http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html It may make a difference whether DFS is in use. + 0 Votes Reponse To Answer PurpleSkys Moderator 1 year ago Try re-posting in the Q&A section.The 'Discussion' forum is for matters of general discussion, not specific problems in search of a solution. The 'Water Cooler' is for non-technical discussions. You can submit a question to 'Q&A' here: http://www.techrepublic.com/forum/questions/post?tag=mantle_skin;content There are TR members who specifically seek out problems in need of a solution. Although there is some overlap between the forums, you'll find more of those members in 'Q&A' than in 'Discussions' or 'Water Cooler'. Be sure to use the voting buttons to provide your feedback. Voting a '+' does not necessarily mean that a given response contained the complete solution to your problem, but that it served to guide you toward it. This is intended to serve as an aid to those who may in the future have a problem similar to yours. If they have a ready source of reference available, perhaps won't need to repeat questions previously asked and answered. If a post did contain the solution to your problem, you can also close the question by marking the helpful post as "The Answer". . + 0 Votes Same issues DjGuardian 1 year ago I saw something on deleting the temp files associated with excel. However, there was always 1 in use that wouldn't let me delete it, even after reboot. If the temp file was a source of the problem, it was problem the one that was locked up. We're using XP with 2003 primarily. Ultimately, the easy fix for my team was for me to just save as a new file, delete the old file and rename the new one to match what the old one was. It was quite a simple solution, but I'm sure this problem will still arise in the future. The same user who was registered as having locked the file has regular issues of varrying kinds, many related to excel. We are sharing the workbook. btw... we are using a completely different anti-virus here. I doubt that has much of anything to do with it. I have seen other people across the net with this issue and the most common relating factor is that the workbook is shared. If it's of any benefit, we did not have any problem with multiple users saving or one logging off as the other was saving as only the one user associated with the lock was the only one using the workbook.