[dba-issues] [Issue 109763] Using Form Based Filterin g and the form: IN Operator the warning dialog regarding (,) vs (;) syntax usage is too vagu e to be useful
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109763 --- Additional comments from eberl...@openoffice.org Fri Dec 10 13:08:06 + 2010 --- Created an attachment (id=75312) Error Msg Version = 330m15 - 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 - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 109763] Using Form Based Filterin g and the form: IN Operator the warning dialog regarding (,) vs (;) syntax usage is too vagu e to be useful
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109763 User oj changed the following: What|Old value |New value CC|'atjensen'|'atjensen,clu' --- Additional comments from o...@openoffice.org Thu Oct 28 06:12:32 + 2010 --- In a DEV300m90 I don't see any error message. Could please add screen shot of the error message? Thanks. - 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 - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 109763] Using Form Based Filterin g and the form: IN Operator the warning dialog regarding (,) vs (;) syntax usage is too vagu e to be useful
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109763 User clu changed the following: What|Old value |New value Assigned to|clu |oj Priority|P3|P4 Target milestone|OOo 3.x |OOo Later --- Additional comments from c...@openoffice.org Mon Aug 16 10:43:46 + 2010 --- clu-oj: in my opinion a rather seldom case, so i would propose to fix it if you rework this area - 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 - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 109763] Using Form Based Filterin g and the form: IN Operator the warning dialog regarding (,) vs (;) syntax usage is too vagu e to be useful
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109763 User atjensen changed the following: What|Old value |New value Assigned to|dbaneedsconfirm |clu Ever confirmed| |1 Status|UNCONFIRMED |NEW Issue type|DEFECT|ENHANCEMENT Keywords| |usability Summary|Filtering form: IN Operato|Using Form Based Filtering |r allows only two expressi| and the form: IN Operator |ons | the warning dialog regard | |ing (,) vs (;) syntax usag | |e is too vague to be usefu | |l Target milestone|--- |OOo 3.x --- Additional comments from atjen...@openoffice.org Thu Mar 18 20:13:38 + 2010 --- @eberlein I just went through this again with DEV300m_75 In your last comment the problem is that you should be using: IN( 1; 2 ) Blanks are of no importance if you use the correct syntax. Two things however - First there is nothing in the help about this, that I can find. That may be poor searching on my part. - Second the error box, correctly displayed IMO, when the incorrect syntax is entered displays a string that is, again IMO, much less useful then it really *need* to be. I am going to change the summary here, move from defect to enhancement, set keyword usability and assign to CLU for UX - 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 - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
