Issue 17994 - nonstandard date formats confuse standard autofilter
Summary: nonstandard date formats confuse standard autofilter
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2003-08-07 23:23 UTC by philmperry
Modified: 2013-02-07 22:34 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description philmperry 2003-08-07 23:23:09 UTC
It appears that the database autofilter "standard" does not appear to be able to
handle a range of dates (on or after first and on or before second) if the dates
are in a nonstandard format, e.g., Jan-99.
Comment 1 frank 2003-08-08 10:24:22 UTC

I don't understand what you want. Please attach a document that shows
your problem and give a step by step description for what you are doing.

Comment 2 philmperry 2003-09-05 01:02:25 UTC
I am changing it to an Enhancement request, as it is now working for
standard format dates (e.g. 12/25/2002). However, it would be nice to
consider additional date formats, such as MMM-YY e.g., dates such as
Jan-99, Mar-00 (A Y2K problem?), Nov-98. A standard filter asking for
dates before Jan-99 should return the Nov-98 record, but it doesn't
return anything. Such date formats appear to be treated as text
instead of dates. As there are many potential date formats, perhaps it
would be easiest to permit users to define their own format converter
macros (to change Jan-99 into 01/01/1999, for example). If a data
field is not recognized as a date or a number (it is considered text),
invoke the macro DATECONV on it to change it into a recognized date
format. A skeleton or example macro sample would be provided to help
users with defining their own converters.
Comment 3 frank 2003-09-05 09:15:18 UTC
Again, I can't understand what you want if you do not provide me with
an document showing your problem.

Please attach such a document or I will close this as invalid.

Comment 4 frank 2003-09-17 12:34:41 UTC
Hi Bettina,

maybe you know what he wants.

Comment 5 philmperry 2003-09-18 03:24:27 UTC
There are many possible date formats; too many for Calc to be able to
recognize. What I'd like to see is the ability for a user to define
the date format they're using to a "DATECONV" date conversion macro.
If a date is not recognized as one of the standard formats then the
macro would be called to output the date in a standard (internal?)
format. Filtering (and possibly other operations) based on this new
date format would then be possible. Calc would supply a sample
DATECONV with one or two format conversions to show how it's done. The
user would then edit DATECONV to support the date format(s) they use. 

I don't know how Calc handles cell contents internally, so it's
possible that if not recognized as a standard date format (or number),
the cell would just be text. That would mean that all text (string)
data would have to be passed through DATECONV for the macro to see if
it should be treated as one of the user's date formats. This of course
would only be done if a standard filter is being defined using that
column. Does this clear up what I want?
Comment 6 ace_dent 2008-05-16 02:40:19 UTC Issue Tracker - Feedback Request.

The Issue you raised has the status 'New' pending further action, but has not
been updated within the last 4 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version:
or consider trying the new OOo 3 BETA (still in testing):
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
Many thanks,
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
Comment 7 bettina.haberer 2010-05-21 14:53:31 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".