We have a word document that has fields in the body of the document that are mapped to the Word properties. We reuse this document as a template for our project work. In this document, in the Properties (in Word 2007 click on the office button/Prepare/Properties/choose Advanced Properties/click on Summary tab) there are properties called Author, Comments, Manager, etc. Each property represents a piece of information that our users type in about their project. For example, the Comments field holds our client name and address. Then, in the body of the file, we have a field mapped to Comments. When the user updates that field (right click/update field) the value that they typed into the Comment field is inserted into the body of the file. Now, the issue...we have default placeholder values in the Properties (like "Insert Client name") that tells our users what to type into the Properties. Ocassionally, we have users who change the properties to add the project information, save the file, upload it to our MOSS application. When the reviewer of the file opens the file, they do not see the project-specific information in the Properties. Instead they see the default information. But, the fields in the body still have the project-specific data. So, the first user updates the properties, but after uploading to Sharepoint, these properties are 'lost'. I have not been able to find anyone else with this issue. Any help would be appreciated.

The version that appears in Central admin is 12.0.0.6421 (is this what you're looking for?). Yes, we have a test site and I am able to reproduce this error. Here is one way that I am able to reproduce it: have an offce 97-2003 word file (.doc) in a library; 'author' property is set to "1110XXXX"; user checks it out and then right clicks on it to Save Target As to their desktop. User edits the properties (changes 'author' property to "11102034") and saves the file as Word Document (.docx). User uploads the file back to initial library and checks it in. Reviewer opens library and launches file (or saves it locally). When reviewer views the properties, he sees "1110XXXX" in the author property. If the original user opens the copy of the file from her desktop, the property is still set to "11102034". The issue is definitely happening when the file is uploaded to Sharepoint.

If you were using Word 2003 or the .doc extension I would say have a look at the following, its a really good read to understand how SharePoint applies metadata... However, since you are using Office 2007 or greater this is not the case and this is not the problem... Uploading files to SharePoint can be done many ways including the upload page, front page extensions remote procedure calls and webdav using Windows Explorer. Of course Microsoft Office uses its own proprietary ways which may involve a combination of webservice and rpc calls depending on what version of Office you are using. Many companies have upgraded to SharePoint 2007 and Office 2007, however; many older Office version files still exist. Companies are putting older Office documents in SharePoint 2007 without converting to Office 2007 format. This seems to be reasonable, until you need to view and edit the document's properties. The catch is the process of "property demotion". SharePoint has a process of property "promotion" and "demotion". When you upload a document and its properties then a document's properties get "promoted" to the matching SharePoint columns. Opening the document from SharePoint then demotes SharePoint properties to the matching document's properties so they can be viewed in the native application. SharePoint 2007 seems to have a problem with the demotion process for Office 2003 documents. Check out the rest of the article Steve Curan Explains this better than anyone... http://sharepointfieldnotes.blogspot.com/2009/09/office-2003-files-are-second-class.htm The main problem is using front page remote procedure call "put document". This method makes a direct call to the author.dll uploading the file binary and the corresponding properties you wish to populate. However, uploading Office 2003 files using this method causes an error on SharePoint 2007. After uploading a file you can examine the metadata that is generated for the document in the "AllDocs" table in the corresponding content database in sql server. Below is an example of what is generated in the metaInfo column of the table when you upload a file. Ok, now I have a couple of questions: You use this document as a template... Do you mean that when you choose File New from a document library with this content type applied this is the template being used? You have the following (Author, Comments, Manager, etc) site columns assigned to a content type and the Ctype is applied to a document library. As an example you have a Site Column "Comment" and the metadata syncs to the document properties Comments so that when comments are added to the document that arte also searchable in SharePoint and used in the body of the document as the address???? Cheers, -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.