Issue 13548 - Paramater Name Substition Fails after two concurrent (form based) filters that yield zero results
Summary: Paramater Name Substition Fails after two concurrent (form based) filters tha...
Status: CLOSED DUPLICATE of issue 11879
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta
Hardware: PC Windows XP
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-17 12:52 UTC by phillg
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description phillg 2003-04-17 12:52:19 UTC
Set-up:  A form (e.g. name & address) with a sub-form linked via Parameter Name
Substitution (e.g. lookup of country code to verbose description).

How to reproduce:  Apply a form-based filter that will generate zero results
(e.g. SURNAME LIKE '123*').  Apply another form-based filter and type over the
existing one (e.g. SURNAME LIKE '456*').  If you change this filter for a third
one that will work (e.g. SURNAME LIKE 'SMITH*') the sub-form results will not
appear.

Other notes:  Applying the filter only once to get zero results and then one
that does works fine (i.e. the sub-form appears).  Closing the form will usually
fix the problem, or in the worse case quiting the quick-starter.
Comment 1 Frank Schönheit 2003-04-17 13:32:05 UTC
phil, can you please check if in your scenario, the "add data only"
property of the sub form has been implicitly set to "yes" during your
filter operations?
Comment 2 phillg 2003-04-17 14:06:39 UTC
No, it is set as "no" on the form and the macro does not attempt to
change it.
Comment 3 Frank Schönheit 2003-04-22 07:54:05 UTC
> No, it is set as "no" on the form and the macro does not attempt to
> change it

Hmm .... (there was a bug that this was implicitly changed) ...
Comment 4 Frank Schönheit 2003-04-28 16:12:03 UTC
phil, because I am lazy: Do you mind creating a small sample document
(.sxw, plus .dbf or e.g. a MySQL script creating sample tables) which
would help reproducing this?
Comment 5 Frank Schönheit 2003-04-30 14:32:17 UTC
phil, I could reproduce this as described by you, but in my scenario
it's really about the "add data only" property: when the filter is
applied the first time, this property is changed to "yes" for the sub
form, which causes it to _not_ display non-existent records.
So unless you can provide an example for this bug which does not
incorporate the "add data only" property of the sub form, I fear this
is a duplicate of issue 11879.
Comment 6 phillg 2003-05-06 10:35:28 UTC
As always Frank you are correct.  The sub-form is changed to Add Data
Only=Yes after the first zero-result filter.  Marking this a duplicate
of issue 11879.  Thanks again...

*** This issue has been marked as a duplicate of 11879 ***
Comment 7 Frank Schönheit 2003-05-06 12:17:50 UTC
> The sub-form is changed to Add Data Only=Yes after the first
> zero-result filter

closing then ... thanks.
Comment 8 hans_werner67 2004-02-02 12:57:37 UTC
change subcomponent to 'none'