To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113554
------- Additional comments from atjen...@openoffice.org Sat Jul 31 06:10:35 +0000 2010 ------- @ameliab Using the database with OO.o 3.2/Ubuntu is a bit different, the office crashes every time. Using OOO330m_2 (the current development build for 3.3) after input a few records and missing data failed writes for a dozen more as test - no crash ever. Using Ubuntu 3.2 to get the crash to stop - open the database, select the menu Edit>Database>Advanced settings. On the dialog remove the tick mark from the item "Form data input checks ....". This stops the crash, the data is never written to the table for a partial record, but it is tossed away, and the main form record pointer moved to the next/prev record. Which I would agree is a design error on Bases default actions in this use case. You can work around it however, see: http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/XRowSetApproveListener.html#approveRowChange But I suppose this issue as to the crash only. --------------------------------------------------------------------- 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
