To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=100040
------- Additional comments from f...@openoffice.org Mon Mar 9 10:25:45 +0000 2009 ------- The error in writing the storage is properly propagated (i.e. raised as exception in the XTransactedObject::commit implementation), but unfortunately the database document silenced this exception in this particular case. I committed code to dba31j which changed this, so now the macro migration properly reports an error. Which doesn't fix the root cause, of course, but at least the data loss. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
