DOORS: Insert OLE with explicit type (aka Show PDF as editable information) - ole

Question

I can insert MS Word files as OLE into a DOORS object, both manually and via DXL, but PDFs (and EPS as well) behave different: it is difficult to make those not appear as icon.
I able to insert a PDF file (showing some graphics) as OLE manually only by using the dialogue's Create New radio button with specifying the type explicitly as Adobe Acrobat Document (without the Display As Icon option). All is well in this case.
Using the radio button Create from File button leads to the same undesired behaviour as using the DXL function insertOle() to insert the object: the result is displayed as icon only.
if (oleInsert(current, "c:\\temp\\27.pdf", false))
print "Successfully embedded document\n"
else
print "Problem trying to embed document\n"
Gives me:
Double-clicking the icon opens the associated application (Acrobat Reader) and shows the embedded PDF properly. However, the OLE properties dialogue displays the type Package. Manual insertion as described above creates an OLE object with the type Adobe Acrobat Document (as specified while creating it).
Inserting a Word document via DXL instead of the PDF makes the embedded document being rendered properly -- apparently the type is determined automatically and correctly:
Apparently, I am not able to (but would have to) specify the OLE type when inserting the PDF.
I am aware of a similar problem at the IBM forum, but the code from there did not even update existing OLE objects but left my objects without any OLE content! Another thread addresses that problem too, but does not provide a detailed solution.

Answer 1

There are two things I would check that would cause a different result for you and your colleague:
Check if they have a full 'edit' version of Adobe Acrobat installed. Since OLE is a Microsoft standard, having Full Acrobat instead of just the Viewer installed may register components with Windows that allow the OLE to display properly for them.
If they do not have Full Acrobat installed, then perhaps they have a different version of the Viewer or a 3rd party PDF viewer that you do not have on your machine.
The DXL reference manual specifically states that An OLE package is created if a file has no associated applications that support OLE. So your system is not recognizing the association, but your colleague's is.

Answer 2

The root cause is still unknown, but the problem was solved eventually. My Windows user account was deleted and created from the scratch. Now it works.
Another colleague has the same problem -- maybe we will take the time and try to isolate file / setting which contained the cause.