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 15:29:29 +0000 2009 ------- > I did it explain, and you returned that you could catch the point, what else > can I do. Answering my questions is a good starting point, as you did with explaining that cycling within the same record still commits the data. I was not aware of the fact that it does so, and I tend to agree that this is a bug. If you submit it, it has chances of being fixed. If you moan about in in a somewhat unrelated issue like this here, it hasn't. > Wvery 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! I disagree. That alone does not mean that the functionality you describe/request is useless. Again, let me ask you to describe the work flow you have in mind in more detail. The most "simple" solution to your problem, as I understand it, is to raise a dialog at every point where today a silent "commit to database" happens, asking the user for confirmation. There could be other (better?) solutions to this, that's why (and to better understand what you request) I asked how the work flow looks in your imagination, sadly without a concrete response. > HSQL is not intended to keep/hold data for updating a back-end until you > leave a form. Huh? Where did I claim this? Sorry, but your complete last paragraph does not make any sense to me. --------------------------------------------------------------------- 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]
