To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104504
--- Additional comments from ville...@openoffice.org Sun Jan 17 07:56:21
+ 2010 ---
Work-around with a pattern field and the right field formatting:
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104504
--- Additional comments from berglun...@openoffice.org Wed Aug 26 06:27:41
+ 2009 ---
fs, I appreciate your time and ask you to give me just a little more.
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104504
--- Additional comments from f...@openoffice.org Wed Aug 26 07:03:38 +
2009 ---
berglundma, I well understand that the behavior is as you described. What I'm
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104504
User berglundma changed the following:
What|Old value |New value
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
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104504
--- Additional comments from f...@openoffice.org Tue Aug 25 20:39:03 +
2009 ---
I'm tempted to resolve this as INVALID or WONTFIX - the scenario you describe
