Issue 14298 - Autofilter fails to select entire spreadsheet contents
Summary: Autofilter fails to select entire spreadsheet contents
Status: CLOSED DUPLICATE of issue 14251
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.3
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: oc
QA Contact: issues@sc
URL: http://cheap.net.au/~writer/autofilte...
Keywords:
: 24036 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-05-09 16:31 UTC by belzecue
Modified: 2004-01-09 10:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description belzecue 2003-05-09 16:31:40 UTC 
See URL for zip package containing original XLS file and imported SXC file.

I imported an Excel 2000 workbook that contains autofilter headings.  I 
clicked on the SIZE column and defined a manual autofilter for SIZE > 20000.  
Near the bottom of the sheet I noticed there were row values for SIZE of less 
than 20000.  On closer inspection I noticed that after clicking on the arrow 
to define the autofilter for that column, the auto-selected area was omitting 
the last dozen or so rows.  Hence, these rows were not being included in the 
filter.  Load the zip package and try it for yourself: look at the 
autoselected range after setting the filter described.
Comment 1 john.marmion 2003-05-09 17:01:22 UTC 
This issue is very similar to issue 14251. The reason the filter 
fails is because the filter is activated against an inbuilt database 
range. This range only covers to row 4744 and not the complete doc 
which extends to row 4755. The work around is to simply delete the 
database range: Data->Define Range.
Comment 2 john.marmion 2003-05-13 18:42:38 UTC 
see also issue 10995 and issue 11594 for further comments

*** This issue has been marked as a duplicate of 14251 ***
Comment 3 oc 2003-05-20 15:24:07 UTC 
closed because duplicate
Comment 4 oc 2004-01-09 10:23:38 UTC 
*** Issue 24036 has been marked as a duplicate of this issue. ***