From: Steve Rindsberg on
I'd look very closely at the file associations and DDE settings if any for the
WMF file extension on both systems where things work right and where they don't.
If there are differences, that might be the key.

I'm not suggesting that you ask anyone to change their code ... I was simply
curious as to why embedding an object was necessary. Sometimes it is. I like
to know these things. ;-)

If it were clearly an application-specific bug, special-casing the code to work
around the bug might be necessary, but since the same apps behave differently on
different systems, it certainly doesn't seem like that'd be the case here.

In article <9095BCFB-7927-4057-BA0D-59E3A5B416AE(a)microsoft.com>, Mike wrote:
> OK. Here are the specifics. The software that my company produces is coded
> (in Visual C++ with Visual Studio 2008) to export a graphic to a Metafile
> Companion file (.WMF file type). Metafile Companion is installed on my local
> computer, and double clicking on any .WMFs on my system launch Metafile
> Companion. The same happens on co-workers' computers. Our software produces
> the .WMFs correctly...they look fine if you open them in Metafile Companion.
>
> One of the options in our software is to "Create Link". This is supposed to
> insert an Object LINK into a Word doc or PowerPoint file, then launch Word or
> PowerPoint and display the .WMF as a full image. It does that on some
> systems, and Alt-F9 shows that it is a LINK. On other systems, including
> mine, this process inserts a large icon that's labeled with the filename, and
> Alt-F9 in Word shows that it is an EMBED Package, not a LINK. Our software
> is not at fault. I know this because...
>
> If I manually launch Word on my system, and open a blank Word 2007 doc /
> Insert tab / on Text panel click Object button / Create from File tab /
> Browse... to the file / turn on "Link to file" / click OK, I get a small icon
> and Alt-F9 shows that it is an EMBED Package. If I do the same on a
> co-worker's system where our software launched Word and displayed the full
> image, the manual insert into Word using "Link to file" creates a LINK and
> displays the full image. Therefore, I conclude that Word and PowerPoint
> settings, or Windows settings, are causing different behavior on different
> systems.
>
> NOTE: Metafile Companion cannot be at fault either. The same manual insert
> of a .jpg using "Link to file" produces the same results...works on some
> systems, doesn't work on others.
>
> I'm not going to ask our programmers to change their code when it's pretty
> obvious that it's not their code that's at fault. Manual procedures in Word
> using any .jpg that has no connection with our applications demonstrates the
> behavior.