To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=36231
------- Additional comments from [email protected] Fri Oct 9 14:42:33 +0000 2009 ------- well Frank I did it explain, and you returned that you could catch the point, what else can I do. Autocommitting is a nasty nonsense-feature, invented by developers, but useless in allday-work. please catch it: Every form or table, that holds data for edit or by new entry, that can be left unintentionally - by TAB or Nav-Keys - and updates data anyway, is worthless for the user! Bind the function to a button, a function-key or an icon, but do not miss to make it available. It is a problem, that you do not have a Database-Parameter-Table for each ODB, where one can store such things, so you need to put it in the Base-Option-dialog. No good place, but the onlyone, if you want to make SetAutoCommit a switchable option. And, bytheway, you just explained, why devolopment of the base-part of OOo is not evoling: HSQL is not intended to keep/hold data for updating a back-end until you leave a form. I do not know where you got that, it must be an OOo-invention, it has nothing to do with HSQL. However, for a database ment for the public it is a useless concept. Everything must be done loud and clear (explicit commit !) and immidiatly - otherwise no subform/lookup-concept will seriously ever work with OOo. And I have thought you wanted make that possible. Martin P.S.: You change the cycle-behaviour anyway: move from last to first field in TAB-order will update - without to ask. --------------------------------------------------------------------- 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: [email protected] For additional commands, e-mail: [email protected]
