MS Word 2007 and XML Publisher

Is the BI Publisher Client certified with MS Word 2007? If not how soon it will be? And the last one does anyone come across major problems with this combination?
Tomas

Tomas -
it isn't certified (at least as of yesterday it wasn't) but I use it b/c unfortunately it is the only version we have licensed.
I have run into problems but don't know if it is related to 2007. Also - a lot of the blogs give directions for 2003 and as you know the menus in 2007 are completely different. It takes some digging around to find the same paths.
Let me know if you are trying to do something specific and I will see if I can answer any questions...although I don't know much!
Rob

Similar Messages

Displaying BLOB of type word doc in XML Publisher pdf output

Hi all,
Please guide me relating the Displaying BLOB of type word doc in XML Publisher pdf output with links or pointers.In the following xml column TRADE_LICENSE_COPY is BLOB when queried from toad and if clicked on the ouput word doc is being opened directly.How to show the column value word doc as attachment in pdf output?
<?xml version="1.0" encoding="UTF-8"?>

<XXTDIC_SUP_REG>
<LIST_G_BASIC_QUSNRY>
<G_BASIC_QUSNRY>
<RESPONSE_ID>194</RESPONSE_ID>
<UAE_REGISTRATION>Yes</UAE_REGISTRATION>
<TRADE_LICENSE_COPY>PK</TRADE_LICENSE_COPY>
<WEBSITE_DETAILS>com</WEBSITE_DETAILS>
<AMERICA_2009_2010>Between 81 and 90 %</AMERICA_2009_2010>
</G_BASIC_QUSNRY>
</LIST_G_BASIC_QUSNRY>
<LIST_G_CONTACTS>
<G_CONTACTS>
<CONTACT_PERSON>MR.NTF1 NTL1</CONTACT_PERSON>
<PHONE_NUMBER>0</PHONE_NUMBER>
<EMAIL_ID>na</EMAIL_ID>
<FAX_NUMBER>0</FAX_NUMBER>
</G_CONTACTS>
<G_CONTACTS>
<CONTACT_PERSON>MR.NTF1 NTL1</CONTACT_PERSON>
<PHONE_NUMBER>0</PHONE_NUMBER>
<EMAIL_ID>na</EMAIL_ID>
<FAX_NUMBER>-</FAX_NUMBER>
</G_CONTACTS>
</LIST_G_CONTACTS>
<LIST_G_SC_QUSNRY>
<G_SC_QUSNRY>
<RESPONSE_ID1>113</RESPONSE_ID1>
<FY3_PROJTYPE_COMMERCIAL>Between 21 and 30 %</FY3_PROJTYPE_COMMERCIAL>
<ENG_INSTALL_CAPABILITY></ENG_INSTALL_CAPABILITY>
<SCM_EXPERIENCE_PARTNERING>Have you had experience of "Partnering"?(i.e with major contracts / employers If so list them.Also please provide details</SCM_EXPERIENCE_PARTNERING>
</G_SC_QUSNRY>
</LIST_G_SC_QUSNRY>
<LIST_G_ADDRESS>
<G_ADDRESS>
<OFFICE_ADDRESS>Addres1</OFFICE_ADDRESS>
<ADDRESS_LINE1>Addre line1</ADDRESS_LINE1>
<ADDRESS_LINE2>Addre line2</ADDRESS_LINE2>
<ADDRESS_LINE3>Addre line3</ADDRESS_LINE3>
<CITY>City1</CITY>
<STATE>State1</STATE>
<COUNTRY>US</COUNTRY>
</G_ADDRESS>
<G_ADDRESS>
<OFFICE_ADDRESS>Addres2</OFFICE_ADDRESS>
<ADDRESS_LINE1>Addre line1</ADDRESS_LINE1>
<ADDRESS_LINE2>Addre line2</ADDRESS_LINE2>
<ADDRESS_LINE3>Addre line3</ADDRESS_LINE3>
<CITY>City2</CITY>
<STATE>State2</STATE>
<COUNTRY>IN</COUNTRY>
</G_ADDRESS>
</LIST_G_ADDRESS>
<LIST_G_DSN_QUSNRY>
</LIST_G_DSN_QUSNRY>
<LIST_G_PROD_SUB_CODE>
<G_PROD_SUB_CODE>
<PROD_SUB_CODE>060.42</PROD_SUB_CODE>
<PROD_SUB_DESC>Automotive Maintenance Items and Repair/Replacement Parts.Filters: Air, Fuel, Oil, Power Steering, Transmission and Water, and PCV Valves</PROD_SUB_DESC>
</G_PROD_SUB_CODE>
<G_PROD_SUB_CODE>
<PROD_SUB_CODE>060.60</PROD_SUB_CODE>
<PROD_SUB_DESC>Automotive Maintenance Items and Repair/Replacement Parts.Hose and Hose Fittings: Brake, Heater, Radiator, Vacuum, Washer, Wiper, etc.</PROD_SUB_DESC>
</G_PROD_SUB_CODE>
<G_PROD_SUB_CODE>
<PROD_SUB_CODE>207.37</PROD_SUB_CODE>
<PROD_SUB_DESC>Computer Accessories and Supplies.CRT Holders, Cases, Glare Screens, Locks, etc.</PROD_SUB_DESC>
</G_PROD_SUB_CODE>
<G_PROD_SUB_CODE>
<PROD_SUB_CODE>207.60</PROD_SUB_CODE>
<PROD_SUB_DESC>Computer Accessories and Supplies.Keyboard Dust Covers, Key Top Covers, Keyboard Drawers, Wrist Supports, etc.</PROD_SUB_DESC>
</G_PROD_SUB_CODE>
</LIST_G_PROD_SUB_CODE>
<LIST_G_CONT_QUSNRY>
</LIST_G_CONT_QUSNRY>
<LIST_G_BUSS_CLASS>
<G_BUSS_CLASS>
<BUSS_CLASS>SUPPLY_CHAIN</BUSS_CLASS>
</G_BUSS_CLASS>
</LIST_G_BUSS_CLASS>
<CF_SUPPLIER_NAME>N1</CF_SUPPLIER_NAME>
<CF_REG_STATUS>Draft</CF_REG_STATUS>
<CF_BUS_CLASS></CF_BUS_CLASS>
<CF_PROD_SUBCODE>060.36</CF_PROD_SUBCODE>
<CF_PROD_SUBCODE_MEAN>Automotive Maintenance Items and Repair/Replacement Parts.Electrical Accessories: Alternators, Ammeters, Coils, Distributors, Generators, Regulators, Starters, etc.</CF_PROD_SUBCODE_MEAN>
<CF_COUNTRY>India</CF_COUNTRY>
</XXTDIC_SUP_REG>
Thanks in advance.
Best Regards,
Mahi

Mahi,
you can't do that yet.

Problems with reports and XML-publisher - No XML

Hi!
I'm having a problem with Apps and XML-publisher. I made a report file, which queries some views. When executing in reports, I get all the data I expect.
Now, when I upload the reportfile to Apps and let it generate XML, my xml-file is empty (well, almost empty)
<?xml version="1.0" ?>

<T03501684>
<LIST_G_PERSOON>
<LIST_G_PERSOON />
</T03501684>
Anyone who can shed any light upon this problem?

OK, finally solved the problem... A good night's sleep always helps ;).
After just trying each queried table one after an other, I found the problem:
The difference between Oracle Apps (Dutch locale) and the reports builder (English) is the language... And our functional people have changed some names, but the Dutch ones, leaving the english names in place and one of the tables I query has language specific data, which is also appears in a where clause.

How to disable 'Save' button when OAF and XML Publisher integrated...URGENT

Hi,
I am new to the OA Framework and XML publisher. I have been working on a requirement where I am designing a new page in Manager Self Service with few fields and a submit button. Also designed a RTF template in XML publisher to display the output in PDF format.
When the details are entered on the page and click on 'Submit' button, the PDF will Open with the data populated. This is working perfectly... thanks to the forum.
But my issue is: When the submit button is clicked, it displayes a dialog box with Open/Save/Cancel options and if I click the 'Open', the PDF will be opened. But my client is a retail client and they don't want store managers to save this PDF so either I have to skip this dialog box and directly open the PDF or I have to disable the 'Save' on the dialog box.
Gurus -- Please help me how to achieve this. This is very urgent
Below is the piece of code I am using in the controller to generate the PDF.
TemplateHelper.processTemplate(
((OADBTransactionImpl)pageContext.getApplicationModule(webBean).getOADBTransaction()).getAppsContext(),
APP_NAME,
TEMPLATE_CODE,
((OADBTransactionImpl)pageContext.getApplicationModule(webBean).getOADBTransaction()).getUserLocale().getLanguage(),
((OADBTransactionImpl)pageContext.getApplicationModule(webBean).getOADBTransaction()).getUserLocale().getCountry(),
inputStream,
TemplateHelper.OUTPUT_TYPE_PDF,
null,
pdfFile);
Thanks in Advance,
Naren

Frank, thanks for the update.
But do you want me to try ControllerContext.getInstance().getCurrentViewPort().isDataDirty(); in button disable property?
I have written one method in my am like
public boolean isTransactionDirty(){
return getDBTransaction.isDity();
and exposed that method to client side and i try to use this method in my button disable property as
disable#{bindings.isTransactionDirty.execute} but this is not working.
Thanks

Can anyone help with a Word 2007 and Acrobat 9 combine files problem?

Hi all
This may be a setup problem but I was unable to find an answer.
I have many word documents that use a style as Heading 1, 2 and 3. What I normally do is to use the Adobe option of "Merge Files into a Single PDF" and then select the documents I want and press combine. Adobe then combines all the documents into a single PDF taking all my headings (styles) and converts them into bookmarks.
I should say that is how I worked until a month ago.
My company upgraded my computer and reinstalled Adobe. Now I have the following problems:
The option of "Merge Files into a Single PDF" is no longer available from the Windows Explorer context menu. It is available from within Adobe.
When I use the option from within Adobe, it does not take the headings into account, so it does not create bookmarks from the styles.
When I create a PDF from within Word, I first check the Adobe Preferences and make sure that the "Convert Word Styles to Bookmarks" option is checked and that my heading styles are checked. Clicking "Create PDF" creates the PDF that I want.
By the way, I am using Word 2007 and Adobe Acrobat 9.

You need to define cell styles for your header and footer rows. Unfortunately there is no setting for cell height. You can force it by using a fixed First Baseline Offset combined with Top and Bottom Insets. This will produce rows that are 1p3 high:

Word 2007 and CSS

Word 2007 (and similarly Outlook 2007) have some limited CSS
rendering capability. Anyone have experience with these. Their
compatibility tool for DM8 shows errors but no solution.

Many people here use newsreaders. Most of the answers posted
come from the
NNTP side....
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"505699" <[email protected]> wrote in
message
news:essdck$ps6$[email protected]..
> Sorry. I did not not realize you were looking via a
newsgroup. I probably
> should not have said anything, but I was a bit surprised
that you called
> this
> person a crackpot when I felt his/her post was clear and
well considered.
> It's
> no big deal. I now realize the person never responded to
your original
> response, so maybe you were right anyway.
>
> "I don't know where he was going, either. Crackpot! 8)"
>

Word 2007 and Excel Chart - Merging

I am in the process of creating a Benefit Statement in Word 2007 and using the mail merge features to import my data from Excel. The only issue I am having is trying to create a pie chart at the bottom of the statement.
Any assistance or advice would be appreciated.

Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with you directly:
http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551

Word 2007 and Outlook 2007 error 1605

Hi,
I keep getting this error with Word 2007 and Outlook 2007:
Microsoft Office word can't open thesaurus. Windows Installer error 1605.
Please advise on how to fix this.

Thank you. Thank you. Thank you. In all my searching for this problem, Yerger's was the only one that made much sense. And it worked! I no longer get an error when I open Outlook, and now I have my thesaurus back in Word!.
I suspect it will also fix the problem I was getting sometimes in Word that some kind of proofing tools were not available (although that was intermittent so I can't really tell for some time.)
Your solution was easy to follow and I like the explanation. I am usually suspicious of making changes to the registry based on an unknown person's suggestions. With this I could easily see that it was the relevant key.
For those not sure how to edit their registry: From the Start Menu, select Run, and type in regedit
Thanks!

JDeveloper and XML Publisher with EBS ?

Hi All,
Can anyone clarify my doubts ?
I am new to Java and i have some experience in XMLP, but i saw in the User guide the Java API's, how to and where to run those API's.
And is JDeveloper used with XMLP to run Java API's ?, if yes can u pls explain how to start working on that and what is the relation between JDeveloper and XML Publisher in EBS.
I really appriciate your early reply.
Thanks in advance.

XML Publisher ships with 2 XDK parsers a 9i version for backward compatibility and 10g version - you can switch at runtim using the properties. However, you have to make sure that the XML Publisher versions of the libraries are used and not the ones coming with i.e. jdeveloper version or oc4j version that you are using. You should use the version shipped with XML Publisher, because these versions are thoroughly tested with XML Publisher.
See the deployment notes in the install document:
Oracle OC4J Deployment Notes
The version of the XML Parser shipped with Oracle OC4J is incompatible with XML Publisher. When you create an XML Publisher application for OC4J you need to configure the system to use the XML Publisher version of the XML Parser. This can be accomplished by setting an orion-web.xml configuration file with the following content:
<?xml version = '1.0' encoding = 'windows-1252'?>
<orion-web-app>
<web-app-class-loader search-local-classes-first="true" />
</orion-web-app>

OAF and XML Publisher

Hi,
How to merge OAF and Xml publisher when multiple view objects are present i.e(PO header and Lines)
Thanks

refer this http://apps2fusion.com/at/ps/260-integrating-xml-publisher-and-oa-framework
--Prasanna

Word 2007 and Windows 7

When opening a document from My Documents, first I am asked if I want to give MS Word permission to make changes on my computer. Then an error message, without a code, "There is a problem sending the commandto the program." To use Word I have to start the program and then open a file. I did not have this problem with Win 7 Beta.
I have run the troubleshooter and checked for compatability. Each time it detects a problem but no fix has worked.
I have uninstalled Office 2007, re-installed, repaired and have installed Office SP2 and nothing has worked.
Any ideas???

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry.
SYMPTOMS
When you use Dynamic Data Exchange (DDE) to send commands to Microsoft Office Word 2003, your custom program may not be able to come to the foreground. If you try to switch focus away from the Word 2003 window, Word 2003 will automatically come to the foreground again. You cannot switch from the Word 2003 document or minimize the Word 2003 window while the DDE commands are being sent to Word 2003.
CAUSE
This problem occurs because every time that Word 2003 obtains a WM_DDE_EXECUTE message from the calling program, it calls the SetForegroundWindow API to force itself into the foreground. As the DDE caller continues to automate Word 2003 through DDE, you will not be able to switch to another application because Word 2003 will come back into the foreground.
RESOLUTION
This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest Office 2003 service pack, you do not have to install the hotfix.
Service pack information
This problem is corrected in Office 2003.
To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
After you install the service pack, follow the steps that are listed in the "More Information" section to set the DontJumpForegroundInDDEExec registry key and to enable the hotfix.
Hotfix information
How to obtain the hotfix
This issue is fixed in the Word 2003 Hotfix.For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the Word 2003 post-Service Pack 1 hotfix package
After you install this hotfix, follow the steps that are listed in the "More Information" section to set the DontJumpForegroundInDDEExec registry key and to enable the hotfix.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Office 2003 Service Pack 2.
MORE INFORMATION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To activate this hotfix, follow these steps:
1.
Quit Word 2003.
2.
Click Start, and then click Run.
3.
In the Open box, type regedit , and then click OK.
4.
Locate and then click to select the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Options
5.
After you select the key that is specified in step 4, point to New on the Edit menu, and then click DWORD.
6.
Type DontJumpForegroundInDDEExec, and then press ENTER.
7.
Right-click DontJumpForegroundInDDEExec, and then click Modify.
8.
In the Value data box, type 1 , and then click OK.
9.
On the File menu, click Exit to quit Registry Editor.
Issues that this fix With package fixes
This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:
When you try to open a Word 2007 document that has nested XML tags applied to the Word document's content, you may receive the following error message:
XML has been disabled in the document as the system has become unstable. Close all programs and restart your computer
In Word 2007, you open a document in a shared network location. Then, you use the Send to Exchange Folder command to send a copy of the document to an Exchange folder. However, when you view the document in the Exchange folder, you see that the document has a Temporary Internet file name instead of the document's original file name.
Consider the following scenario:
You save a Word Macro-Enabled Template (*.dotm) file in one of the following STARTUP folders:
Drive :\Users\ user name \AppData\Roaming\Microsoft\Word\STARTUP
Drive :\Program Files\Microsoft Office\Office12\STARTUP
You start an instance of Word 2007.
When you run the winword.exe /automation command to start a second instance of Word 2007, you may receive the following error message:
File In Use
file name is locked for editing by ' user name '. Do you want to:
Open a Read Only Copy
Create a local copy and merge your changes later
Receive notification when the original copy is available
Note In the error message, file name is the name of the Word Macro-Enabled Template (*.dotm) file that you saved in the STARTUP folder. BUG #:
MORE INFORMATION
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
There are no prerequisites for installing this hotfix.
Restart information
You do not have to restart the computer after you apply this hotfix.
Hot fix replacement information
This hot fix does not replace a previously released hot fix.
Registry information
You do not have to make any changes to the registry to apply this hot fix.
This hotfix is scheduled to be included with 2007 Microsoft Office Suite Service Pack 2.
NOTE - Disclaimer
By using the following materials or sample code you agree to be bound by the license terms below and the Microsoft Partner Program Agreement the terms of which are incorporated herein by this reference. These license terms are an agreement between Microsoft Corporation (or, if applicable based on where you are located, on of its affiliates) and you. Any materials (other than sample code) we provide to you are for your internal use only. Any sample code is provided for the purpose of illustration only and is not intended to be used in a production environment. We grant you a nonexclusive, royalty-free right to use and modify the sample code and to reproduce and distribute the object code form of the sample code, provided that you agree: (i) to not use Microsoft's name, logo, or trademarks to market your software produced in which the sample code is embedded; (ii) to include a valid copyright notice on your software product in which the sample code is embedded; (iii) to provide on behalf of and for the benefit of your subcontractors a disclaimer of warranties, exclusion of liability for indirect and consequential damages and a responsible limitation of liability; and (iv) to indemnify, hold harmless, and defend Microsoft, its affiliates and suppliers from and against any third party claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of the sample code.

Generating pdf report via concurrent manager and xml publisher

I have report (rdf) which works fine in eBusiness Suite but Id like to create translatable reports with reach layout (comparing with the Report Builder) based on the functionalities of the XML publisher. Ive made all necessary steps (first change the output format for that report in concurrent manager from pdf to xml, submit the report to get xml file, which Ive used in Microsoft Word Template Builder to make layout in rtf file, and create data and template in XML Publisher Administrator in eBusiness Suite).
When Ive submitted that report from concurrent manager, after the concurrent manage finished his job I got the warning message.
Also the output file is not generated and in log file there is a message: One or more post-processing actions failed. Consult the OPP service log for details.
Concurrent manager works fine, but there are problem when concurrent manager send the xml output of the report to XML Publisher which have to create pdf layout based on rtf template.
I think there might be a problem with report complexity, while Ive used layout formatting, api calls to eBusiness Suite, parameters, placeholders, attached library etc.
If it is impossible to get new report based on xml publisher template, what is the purpose of xml publisher if it is so limited, while every eBusiness Suite Report is so complex.
I hope there will be a person on this forum with the same problem, otherwise Ill give up at all from XML Publisher, at least until it come a better version of that tool which it seems to be in early development phase and not ready for the market yet.

All of the complex report logic is handled in your Oracle Report (rdf) file.
If your Oracle report is working OK, then this report should be generating XML.
After running your report, go to the View Requests window. Highlight your request, and click the Diagnostics button. Then click the 'View XML' button. If you see XML data, then you should be OK.
When I faced a similar issue, it was because the '1 step' process didnt work for the particular report I was using. The '1 step' process doesn't work for every report. Which report are you using?
If the report is submitted via a form (not the concurrent manager request form), then you probably need to use 2 steps to produce the desired output.
For more information, see the following thread:
Enhancment to avoid 2 step check printing
HTH,
Mark K

MS Word 2010 and BI publisher

Is BI Publisher 10.1.3.4.1 suppose to be able to work with MS Word 2010. I get an error that macros are not enabled which others had alluded to and then tried to go back to Word 2007. Is there an upgrade or patch available to work with Word 2010?

Finally figured out what is the root cause of this issue is. This is caused by one of the Microsoft's windows security update that installs VBA runtime file, which is supposed to fix a VBA vulnerability but caused third party softwares (plug-in) stop working! Yes, this third party software in this case is the Template Builder.
Here is the detail of the MSFT update patch.
http://support.microsoft.com/default.aspx?scid=kb;en-us;932349
Basically what we need to do is to delete '.exd' files, which have been invalidated by the update, then refresh them by restarting the Word again. In my case, I found one file under C:\Documents and Settings\Administrator\Application Data\Microsoft\Forms so deleted it, then restarted Word, now it's all working.
Let me know if this would address your issue.

Dunning Letters and XML Publisher

I have created a template for the dunning letter print in applications. When we submit the dunning letter generate process it kicks off the print automatically and this gives us a problem as the print doesn't seem to have the XMLP template associated with it and we get no output. We can work round this by submitting the XML Report Publisher Request to get the dunning letter print as required. We do have the "one step" patch applied and other XML Publisher reports are working seamlessly so how do we get the dunning letters print to work seamlessly when we have no control of the submission?
Any help appreciated.
Thanks,
Dave

Tim
Yes it works fine in preview. Also works OK if I submit XML Report Publisher.
The problem is the template is for the dunning letters print report but we don't actually submit that, we submit the dunning letters generate which kicks off the dunning letter print. I guess the submit process within the generate process does not include the template in the parameters list so there is no output available when it runs.
Only thing I can think of is to modify the print report to submit the XML Report Publisher in the after report trigger but not sure if this is going to work?
I did see a similar query on metalink where the person was told there would be a solution in XMLP5.5 but I can't see anything in the about 5.5 doc that fits this issue.
Any ideas appreciated.
Thanks,
Dave

Inability to use eps graphics in Word 2007 and make a pdf

Hi there …
I work at a small "intellectual capital" company where virtually all of our documents (our products!) depend on embedding eps "pictures" into Word and pdf'ing the result. While this process works great in Word 2003, it fails miserably in Word 2007 - the "mechanics" work fine and a pdf is produced, but the rendering of the eps images are terrible. I spent some effort looking into this issue trying to find a solution and came up with the following (thanks in part to this post) ... if anyone has any more details, corrections, or solutions feel free to post!
It appears that, over the years, there have been three flavors of eps import filters for Word ... (for the curious the filter is found in Program Files\Common Files\Microsoft Shared\Grphflt\EPSIMP32.FLT )
The simplest (and oldest) filter basically embeds the eps code unmodified into the Word doc and will display a raster preview of the image if one is included in the eps file. if the file is printed on a postscript printer or to Acrobat, the eps code is passed through (so it produces perfect pdfs, and the screen image in Word looks as good as the preview image embedded in the eps file). if the file is printed to a generic printer, no image appears (so it doesn't work for joe user).
The Word 2003-era filter pastes the eps code unmodified into the Word doc, then renders a (very poor) preview image (using an OEM'd eps converter). if a preview image is in the eps file it is ignored (which is bad). if the file is printed on a postscript printer or to Acrobat, the unmodified eps code is passed through (so it produces perfect pdfs, though the screen image in Word looks yucky). if the file is printed to a generic printer, the poorly rendered preview image is printed (so it works poorly but better than nothing for joe user - and probably gives joe user a bad impression of eps).
In what might be an attempt to improve things for joe user, the Word 2007 filter immediately interprets the eps code (using a slightly updated eps converter from the same OEM) and pastes the resulting rendered image into Word. It NO LONGER embeds the unmodified eps code in the Word doc. While the rendered image looks better than filter #2, it still leaves A LOT to be desired - in my brief testing, colors are VERY wrong and curves become choppy. if the file is printed on a postscript printer or to Acrobat, the poorly rendered image is used since the original eps code is gone (unacceptable for my purposes). if the file is printed to a generic printer, the poorly rendered image is printed (so it works better than Word 2003 for joe user).
So where does this leave anyone that wants to upgrade to Word 2007, use eps images, and make quality pdfs ??
Filters #1 & #2 were interchangeable in Word 2003. The true eps experts like #1 the best, and it is by far the simplest technically (76k of code vs 400+k), so they merrily swapped and used it with Word 2003. (Very) unfortunately filters #1 and #2 do not work with Word 2007 - if they did the problem would be nicely solved.
Find another graphics file format to work with? This is undesirable because the "beauty" of #1 & #2 above is the unmodified eps code gets fed to the pdf maker (which itself is native eps) - Word is just a transport (no "transcoding" loss in compression-speak). if there were an efficient way to convert eps to say wmf (microsoft's proprietary vector graphic format), and the images were able to survive two transcodes (from eps to wmf back to eps for pdf), it might be livable. But of course Adobe Illustrator cannot save as wmv (nor should it IMHO). Of note - there is another industry standard vector format - svg - which AI can save as but Word does not support.
Stay in Word 2003 doc format while using Word 2007 (don't use docx). Doesn't work. My testing shows a Word 2003 doc file with embedded eps created in Word 2003 (and pdf's correctly in Word 2003) does not pdf correctly in Word 2007.
Use a work-around. As suggested here, "Open the EPS in Illustrator. Select all, and Edit > Copy. In Word, Edit > Paste Special > Enhanced Metafile." This seems to work for small images such as logos, but not for larger graphical stuff (probably because of the internal transcoding to WMF).
Stay with Word 2003. This appears to be the only workable option for now IF you want to use Word and render eps pictures in pdf's with acceptable quality.
IMHO the best solution would be to have the very simple 76k filter #1 ported to Word 2007 (those who need the capability can swap the filter files) or (not as optimal but does not require swapping filter files) add the option in filter #3 to still embed the eps code. Microsoft is the right place to do it, or (politics aside), Adobe could and should do it (given some support from MSFT).
I am surprised this issue has not caused more rumblings from users - perhaps it has, the symptoms are just worded differently. Or maybe everyone is just staying with Word 2003 (which is what I have done until now). The problem is most companies are being forced to upgrade now, so I think this will become a bigger issue for Adobe / Microsoft going forward.
Thanks for listening. I look forward to your comments.
Andy

Microsoft has released a hot fix that supposedly addresses this issue, it is at
http://support.microsoft.com/kb/977468
I downloaded the fix and tried it; it actually made the problem worse! Apparently they
are trying to fix their filter rather than bypassing it. What I am doing is
1. Making maps in AutoCaD Map and printing (plotting in autocad) them to a pdf file
2. Opening the pdf file in Acrobat and resaving it as eps
3. Importing the eps file into a Word 2007 document
4. Use Acrobat to convert the Word document to pdf
Before the hot fix when I did the process the resolution of the map in the final
pdf file was not as good as in the original made from AutoCad. Also the colors were
not correct. After installing the hotfix there are still these same problems but also now
any non horizontal text is not displaying correctly.
Be careful about trying this hotfix.
As others have noted, back in Word 2003 the above steps 1 - 4 worked very well and resulted
in a high quality pdf file with the map as good as in the original pdf.

MS Word 2007 and XML Publisher

Similar Messages

Maybe you are looking for