Hi, I've just noticed an issue where my windows 7 laptop is not actually saving my files back to the network share where they're located. As an example I have an Excel file that I have been making weekly changes to over several years. If I look at the file on my Windows 7 laptop in Windows Explorer it shows the last modified date for the file as today's date and if I open it all my changes are in there. If I then log into our Windows 2003 Terminal Server as myself and browse to my network folder it shows the last modified date on the network share for the excel file as Oct 2009. And if I open it all my changes aren't there. Basically if I look at this file from any other computer apart from my Win7 Laptop (and this includes the file server where the actual file actually is), it shows that it hasn't been modified since 2009, which is really scary!! It seems like Windows 7 is somehow keeping a local copy of the file on the laptop that it opens whenever I go to the network share and try and open this file (This seems to be proved by the fact I can open this file in Excel on the Terminal Server, and if I then open the file on my laptop it doesn't say anything about the file already being open and do I want to look at it in 'Read Only' mode). Is this normal behaviour, and how do you go about setting it so it doesn't do this? I have 'Offline Files' turned off so it can't be anything to do with a synchronisation problem. I'm running Windows 7 Ultimate with all patches up to date. And Office 2007 SP2. (I've never had this problem running Office 2007 on Windows XP). (NOTE: I came across a similar issue a while back where someone was using a Windows Vista PC. The computer needed to be rebuilt because of an issue, and when we went back in to look at one of their network files they had constantly be changing and saving, the actual version on the network hadn't been modified for over a year. So in that case because it was somehow keeping a local copy of the file we lost all their changes due to the pc having to be rebuilt). Thanks.

Just to add further to this. It seems to be happening to all Office files saved in compatibility mode format (eg. DOC, XLS, etc...). However I still class this as a Windows 7/Office 2007 issue as this problem doesn't seem to happen on win XP running Office 2007. Here are two more examples: USING XLSX FORMAT - I can create a brand new excel file on my laptop and save it to the network location as TEST.xlsx - I can see this file on the Terminal Server and it will show all the content I entered - I then open the file again on my Win7 Laptop make some changes, save and close - I open up the file again on the Terminal Server and all the new changes I've just made are visible, and it has the correct "Modified Date" on the file in Windows Explorer. USING XLS FORMAT - I create a brand new file on my Win7 Laptop and save it to the network location as TEST2.xls - I can see this file on the Terminal Server and it will show all the content I entered - I then open the file again on my laptop (opens in "Compatibility mode"), and make some changes, save and close - I reopen the file on the Terminal Server and I DON'T see the new changes, as well as the "Modified Date" on windows explorer not being updated

Hi, Thanks for posting in Microsoft TechNet forums. Can you reproduce this issue on notepad? Please refer to the following threads for more information: http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/1ec787ca-71c9-4d0d-b7fe-869969b5dcf3 http://social.technet.microsoft.com/Forums/en-US/w7itproappcompat/thread/fe2dd0b0-c831-45ef-bb56-501e4fae53c7 Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Thanks for posting in Microsoft TechNet forums. As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.