• It must be possible to rotate the chart — after embedding it or on the way.
• The embedded chart must be resizable without quality loss, i.e. it must transformed into in some kind of vectorized form, or in very high resolution.
• The Word file must be readable & editable on machines where MS Project isn’t installed (in order to collaboratively edit a document).
• The resulting Word document must not exceed a reasonable size, i.e. its okay for a document to gain a few MB by adding a one-page chart.
• The process of converting/embedding must be reasonably simple so that it can be repeated iteratively, i.e. it shouldn’t take more than a fistful of steps.

According to my personal experience, its an almost impossible job to do. After researching this problem and doing some tedious trial-and-error work for several hours, I found a way:

• print the chart as a high-quality PDF with embedded fonts using Adobe’s PDF driver
• open the PDF in Acrobat
• rotate
• save as EPS
• insert the EPS into the Word doc

This works — if I perform these steps on my colleague’s machine. I tried this on my machine, but it won’t work. Exporting from Acrobat as Word doc works sometimes, but shows rather indeterministic behavior and sometimes leads to a mangled mess. Other approaches, such as going via WMF, EMF or directly embedding the MPP as an object, failed right away.
I assume there is an easier way to do this which works on any machine (with the necessary software) — any suggestions?

For example, I had a Java class which I wanted to create a web service from. No problem, I thought, the Web Standard Tools in Eclipse have a wizard for that. Next time, I will do it by hand, because of several problems:

• That specific wizard crashed in about two of three times I ran it
• When it ran through, the wizard left me with a feeling that I had not learned anything about the process of creating a web service from a Java class. The only things I learned is to use some voodoo and guessing for which values I had to fill in the wizard’s forms.
• The wizard did not tell me in advance which generated source code it would overwrite. So at first run, some of my troublesome hand-coded classes were overwritten. Thank God for version control.

As a conclusion, I tend to use wizards only when I …

1. … am sure that the wizard solves a problem faster than (and in the same way as) I could write the code by hand.
2. … have a rough idea of what the wizard is doing under the hood.