> This very strange; can you check if saving via storeToURL() fails also > if you call it from OOo Basic? This would allow to verify your problem > what we otherwise couldn't do easily, as we don't have your application. > The error code looks strange, if I decoded it correctly it could point > to a problem with recursive OLE objects, but then I don't understand why > saving via GUI works. So the best thing would be if your problem could > be reproduced.
Calling storeToURL() via OOo Basic macro works. Does it mean it is a CLI-UNO-specific problem? I verified that the output file gets created before the exception is thrown, so I guess that the save operation must fail during the save process, which would indicate it is called properly. > In case you are still interested in debugging ;-), you could try to > catch an IOException after the call to the SwXMLWriter. This should show > you the place where it is thrown and perhaps give us a clue what the > root cause may be. You could also pass an InteractionHandler instance in > your MediaDescriptor that will catch the exception for you and - if we > are lucky! - will give a better error message. Of course then catching > the naughty exception would be easiert also as you don't need to catch > all C++ exceptions in the debugger but instead of that set a breakpoint > in the InteractionHandler code (module uui). I've tried to pass the InteractionHandler but it does not get called. I suppose I passed it correctly because it gets called for other errors (like if I try to save to a location without write permissions). I guess the last thing I can try is to catch the exception in OOo process in SwXMLWriter like you say. I'll try that, it will just take me some time because I have to prepare OOo build environment and build it. Is there by any chance an OOo debug-build with debugging symbols (preferrably for Visual Studio) available for download somewhere? Thanks, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
