Issue 78753

Summary: OLE Object Cannot be edited when saved on a PPT file
Product: Impress Reporter: imarobles <imarpubmail>
Component: save-exportAssignee: christian.guenther
Status: CLOSED FIXED QA Contact: issues@graphics <issues>
Severity: Trivial    
Priority: P3 CC: issues,
Version: OOo 2.2   
Target Milestone: OOo 3.1   
Hardware: HP (PA-RISC)   
OS: Windows XP   
Issue Type: PATCH Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 72764    
Description Flags
PPT file that has an OLE Object, cannot be edited on OO2.1
ODP file with OLE Object.
A patch to fix this issue none

Description imarobles 2007-06-21 13:52:54 UTC
I cannot edit my OLE Object (Calc Object) after i re-open my saved file (as PPT).
This only happened after i upgraded from OO2.1 to OO2.2, and until OO2.2.1.

I tried saving to .ODP, the OLE Object can now be accessed.
Comment 1 imarobles 2007-06-21 13:55:08 UTC
Created attachment 46144 [details]
PPT file that has an OLE Object, cannot be edited on OO2.1
Comment 2 imarobles 2007-06-21 13:56:15 UTC
Created attachment 46145 [details]
ODP file with OLE Object.
Comment 3 christian.guenther 2007-09-14 10:41:40 UTC
Set to new and change the target
Comment 4 christian.guenther 2007-09-14 10:45:20 UTC
I can reproduce that I can't open the OLE in the attached PPT-document.
While loading the ppt-file and when I try to open the OLE I get a general
input/output Error.
When I export the attached odp-Document to PPT everything works fine.
Please have a look, whats wrong with the ppt-Document.
Comment 5 mikhail.voytenko 2008-10-07 16:38:21 UTC
The problem here is that the OLE object ins ppt document is OOo OLE object, that
is broken ( a wrong filter has been used to store the contents ). There was a
problem long time ago ( in OOo2.2 if I am not wrong ) that caused generation of
such objects.
Comment 6 2008-11-20 05:27:36 UTC
Created attachment 58130 [details]
A patch to fix this issue
Comment 7 mikhail.voytenko 2008-11-20 18:04:24 UTC
Thanks, I will integrate the patch in one of the next framework childworkspaces.
Comment 8 mikhail.voytenko 2008-11-21 15:03:59 UTC
The patch is integrated in fwk92
Comment 9 mikhail.voytenko 2008-11-24 17:39:13 UTC
mav->cgu: please verify the issue
Comment 10 wolframgarten 2008-12-05 11:26:35 UTC
Verified in CWS.
Comment 11 thorsten.ziehm 2009-07-20 14:54:44 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
If you want to know more about the handling of fixed/verified issues =>
Comment 12 thorsten.ziehm 2009-07-20 15:36:30 UTC
Sorry this issue was wrongly closed. This issue will be reopened automatically.
And will be set after that back to fixed/verified.
Comment 13 thorsten.ziehm 2009-07-20 15:40:49 UTC
Set to state 'fixed'.
Comment 14 thorsten.ziehm 2009-07-20 15:44:51 UTC
Set back to state 'verified/fixed'.

Again. Sorry for the mass of mails.
Comment 15 marcis 2009-11-09 21:30:18 UTC

This bug should be reopened as I've just encountered this same exact issue with
a document I've been sent.

The original document was a pptx and I opened it under Impress 3.1.1 but I
couldn't edit the embedded excel table.

Thinking it might have been a ppt/excel conversion issue, I recreated the table
in calc and inserted it back as an OLE object and saved the document back as a
.ppt but when I tried to open it back up, the same issue popped up (unable to
edit the OLE object).

Saving as .odp keeps the OLE object editable.
Comment 16 thorsten.ziehm 2010-02-22 15:09:29 UTC
This issue is closed automatically. It should be fixed in a version with is
available for longer than half a year (OOo 3.1). If you think this issue isn't
fixed in the current version (OOo 3.2) please reopen it. But then please pay
attention about the field 'target milestone'.
The closure was approved by the Release Status Meeting at 22nd of February 2010
and it is based on the issue handling guideline for fixed/verified issues  :