Bug 82720

What do you mean with "wildcard filter"?
Where do you set the filter? In the mainform or in the subform?
Could you please add an attachment, which shows this bug?

Wildcard filter means one textbox in which no, one, or several character(s) can be typed in with a button to refresh the form.
The textbox is in the main form.
Refresh button and table to show the filtered results are in the first subform.
Refreshes properly.
Three more tables inside this first subform and subforms themselves do not refresh until the document is closed and reopened (only with 4.3 versions).

Addendum: you will get the exact same behavior with the "Media_without_Macros.odb" document illustrating Base Handbook.

(In reply to comment #3)
> Addendum: you will get the exact same behavior with the
> "Media_without_Macros.odb" document illustrating Base Handbook.

I have created this database. Please write down which form you are using. Have just tested a little bit with LO 4.3.0.4. Couldn't confirm any buggy behavior.

Please go to the "Loan" form. Type for instance "g" in the filter textbox.
You'll get Garbo and Gerd as a result. The "Loan" table is correctly updated, as is the name field beneath (Loan for Reader ...).
The "Return" table doesn't refresh.
Plus, shifting between records in the "Loan" table doesn't either make this "Return" table change its display.
Checked again 2 minutes ago on a 4.3.0.4 version (dismantled the dev one).

Created attachment 104769 [details]
Refreshing in SubSubForm doesn't work

open the form.
Change Forname from "Robert" (ID 1) to "Belinda" (ID 2).
The subform will show the values for Belinda, the subsubform, created by the same table, won't.
Works with all Versions up to the last 4.2, doesn't work wil LO 4.3 alpa0 up to 4.3.0.4.
Tested with OpenSuSE 12.3 64bit rpm Linux.
Has nothing to do with a filter, so I will change the title also.

Problem isn't only navigation through the data. Input in subsubforms seems to be broken by the missing connection. See the added bugs.
I will set the importance to high and critical. Many databases wouldn't work any more with LO 4.3 ...

Confirming this behavior using LO v4.3 with Mac OSX (6.8). Reverting to LO v.4.2.5 fixed the problem. (LO v.4.3 is unusable for me because of this critical breakdown of Base functionality.)

It's a duplicate of Bug82151, which has been fixed for LO 4.3.2.

*** This bug has been marked as a duplicate of bug 82151 ***

(In reply to comment #6)
> Created attachment 104769 [details]
> Refreshing in SubSubForm doesn't work
> 
> open the form.
> Change Forname from "Robert" (ID 1) to "Belinda" (ID 2).
> The subform will show the values for Belinda, the subsubform, created by the
> same table, won't.
> Works with all Versions up to the last 4.2, doesn't work wil LO 4.3 alpa0 up
> to 4.3.0.4.
> Tested with OpenSuSE 12.3 64bit rpm Linux.
> Has nothing to do with a filter, so I will change the title also.

I have opened the attachment 104769 [details] using Version: 4.4.0.0.alpha0+
Build ID: b6da6a887a0417be02e123a6d19837123e58b94f
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-08-09_07:47:21 (deb x86 Kubuntu 14.04)

I had no problem adding information to the subform. Then I was able to cycle through the rows of the main form and what I had added appear when it should including matching values of the primary-foreign key pairs.

Another comment: This attachment contains a form with a main form and two identical subforms. This does not qualify as a form with a main form, and subform which also has a subform. To qualify, one of the subforms must have a subform with a foreign key that matches the primary key of the main form. The second subform must have a foreign key that matches the primary key of the first subform.

(In reply to comment #10)
> 
> I had no problem adding information to the subform. Then I was able to cycle
> through the rows of the main form and what I had added appear when it should
> including matching values of the primary-foreign key pairs.
> 
> Another comment: This attachment contains a form with a main form and two
> identical subforms. This does not qualify as a form with a main form, and
> subform which also has a subform. To qualify, one of the subforms must have
> a subform with a foreign key that matches the primary key of the main form.
> The second subform must have a foreign key that matches the primary key of
> the first subform.

Hi Dan,

the example isn't created for adding data or show a full qualified database. See the content of this bug. It should only show the refreshing of a subsubform. And exact this is, what it is doing:

If you do the steps written down in comment6 you see no refresh with LO 4.3.* (last version here 4.3.1.1). But you would see it with the actual 4.4.0.0alpha. The reason for this is the same as in the other reported bugs.

Regards

Robert