To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104504 Issue #|104504 Summary|TimeField/FormattedField badly handle 24 hour time Component|Database access Version|OOO310m11 Platform|PC URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|none Assigned to|dbaneedsconfirm Reported by|berglundma
------- Additional comments from berglun...@openoffice.org Tue Aug 25 19:25:59 +0000 2009 ------- When using a timefield or formattedfield (formatted to deal with 24 hour time) it seems that the field does not handle input well. You *must* enter the data with a colon. If you enter a number like 2345, while this may be a valid time, it is rounded to 00:00. Additionally if you enter any number below 2147 you are returned 23:59. It seems that once you go over 2148 (inclusive) the algorithm rolls over to 00:00. We are currently writing macros to get around this for non-programming types. My (and my coworkers) expectations are that if a 4 digit number is entered, it is treated as a evaluate as a time (0000 to 2359). It seems pedantic to require the user to enter the colon (or formatting symbols which can be assumed) so long as the number is a properly formatted integer for the type. I will be checking this on other systems as I can. --------------------------------------------------------------------- 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
