I opened a post in this forum site about the message above over a week ago. Here is what I asked . . .
"Since installing the latest Service Pack for Office 2010 users, they are receiving the following message when saving an excel file that lives on a shared drive on our File server . . .
"The file "Excel File Name" may have been changed by another user since you last saved it. In that case, what do you want to do?"
The options are "Save a Copy or Overwrite Changes". We only receive this message when saving the file a second time while it is still opened. This wasn't occuring before implementing SP2. I've read that this behavior was also present in other versions of office.
Is this something that was supposed to be implemented is SP2? I did not see it mentioned in the Office 2010 SP2 release notes. "
A tech responded with the following . . .
"
Hi,
Try the following steps:
To resolve this issue in Excel, follow these steps:
1.Click Start, click Run, type regedit, and then press ENTER.
2.Locate and then click the following key:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\14.0\Excel\Options
3.On the Edit menu, point to New, and then click DWORD Value.
4.Type QFE_Saskatchewan for the name, and then press ENTER.
5.Right-click the QFE_Saskatchewan entry, and then click Modify.
6.In the Value box, type 2. When you type this value, Excel will always flush the file cache before the program obtains the time stamp. (This should resolve the problem most of the time.) Or, type 1 to have Excel disable the time stamp check and suppress the
dialog in every case.
Note We do not recommend disabling the time stamp check.
7.Click OK to save the setting."
However that didn't asnser my question so I responded with . . .
"Thanks. This fix does work. I've seen this fix in other forums.
But what I want to know is if this behavior was supposed to be implemented with Office 2010 SP2 or if there is an underlying issue with the Service pack or our network environment.
Any ideas?"
Can anyone help with this. I know about the workaround but want to know if Excel is suppose to behave like this now with SP2. It wasn't behaving like this before SP2.
Pete Macias