Here is my environment: Sharepoint MOSS 2007: Server 2008 R2: Office 2007: Windows XP Client I have sharepoint list that simply lists a number of projects. The columns are ID (system generated) and Project Name. I have setup a site column called LSS Project Name that performs a lookup on the Projects List - Project Name column. I then have created a Site Content Type called LSS Define and have it linked to a word template. In the Word 2007 template, I have the Documents Properties showing up in the information pane and I am inserting the LSS Project Name property into the document using the Quick Parts. When I open a new document from Sharepoint using the Content Type, I can select my project list fromthe LSS Project Name pulldown on the Information Pane. However, in the Word document itself, the ID column is displaying, not the actual project name. If I save the document back to my sharepoint library, and view the properties, the LSS Project Name property displays properly. It is only in the Word document that the Quick Part is not displaying correctly. I should note that I have other Quick Parts in the document that work properly, it is just this one column that is setup as a lookup to a sharepoint list. I even completely deleted the content type and the site column and started over, but with no change. Is this just a limitation of Sharepoint / Office 2007 integration or am I doing something wrong. Thanks, TIm Olig

As far as i remember there was always a problem with Quick Parts using lookups and i still know any workarounds. Actually it was one of the reasons why my company Novitas started SharePoint Reports and Documents Generator project. Also note that there are some unexpected behavior when using Quick Parts with calculated or multi valued columns.

I too am having this same problem, with pretty much the same environment (except WSS 3 rather MOSS). The only thing I would add, is that I can get it to work sometimes, then, sooner or later it stops working (very frustrating...) Has anyone any work arounds, solutions and/or is there a patch? Does anyone know if this will be fixed in Sharepoint 2010? Thanks. J.