To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=106805
User fs changed the following:
What |Old value |New value
================================================================================
Status|NEW |RESOLVED
--------------------------------------------------------------------------------
Resolution| |DUPLICATE
--------------------------------------------------------------------------------
------- Additional comments from f...@openoffice.org Fri Nov 13 13:01:23 +0000
2009 -------
This is a duplicate of issue 106574. In both cases, there is a form with a sub
form, the sub form containing a table control, and the main form is being moved
to the insertion row.
This raises an exception which is not caught. On Windows, OOo continues to
(halfway) work, "only" corrupting some internal states, which leads to the
symptoms described in issue 106574.
On Unix systems, the uncaught exception simply crashes OOo (which is surely the
"better" thing ...).
So, with fixing issue 106574 (in CWS dba32j, targeted for 3.2), this issue here
is fixed as well.
*** This issue has been marked as a duplicate of 106574 ***
---------------------------------------------------------------------
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...@api.openoffice.org
For additional commands, e-mail: issues-h...@api.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
