Description: NOTE: My Split database is FULLY functional with 6.1.6.3 I just upgraded to 6.2.7 and searching using a form fails (permanently HANGS) for combo-forms. In fact, I never get the chance to type anything into the search form -- it is DEAD! Combo-form: I have tables that are linked and parts of 2 different tables are shown in a single form. Data is shown properly in a combo-form. When I try do a simple search, libreoffice HANGS before I can type anything into the search-form. Forms that only have information from 1 table can be searched. I am using hsql in a split database format -- I got tired of the crashes when hsql was internal. See https://www.businessprogrammer.com/create-libreoffice-base-split-database/ for an example setup. I am currently using hsql 2.4.1 Steps to Reproduce: Contact me and I will send a database package that reproduces this problem. I will not send MY database as it has sensitive info. Actual Results: searching combo-forms fails. One CANNOT type into the search form Expected Results: One can type into search form and execute the search! Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: FormDesign [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
Is this problem a duplicate of Bug 123962 - Form based filter search freezes LO with main form and subform? https://bugs.documentfoundation.org/show_bug.cgi?id=123962 If so, the problem seems to be fixed in LO Base LO version 6.3.x
I will try 6.3. and see if it is fixed. Thanks! I will report back later....
Hi, After a bit of testing, it seems that 6.3 fixes this problem for me. You can clear this bug. I was under the impression that the odd numbered set (like 6.3) was "less stable" and that I should use the even ones (like 6.2) to stay out of trouble. It appears that bug fixes are NOT back-ported (like to the 6.2 series)??? In this case, a fairly severe bug was fixed by going "forward" to the "less stable" series and the comment "This version is slightly older and does not have the latest features, but it has been tested for longer. For business deployments, we strongly recommend support from certified partners which also offer long-term support versions of LibreOffice." is not always "accurate". Thanks for your quick help! Ralph Peters
(In reply to Ralph Peters from comment #3) > Hi, > > After a bit of testing, it seems that 6.3 fixes this problem for me. You > can clear this bug. > > I was under the impression that the odd numbered set (like 6.3) was "less > stable" and that I should use the even ones (like 6.2) to stay out of > trouble. It appears that bug fixes are NOT back-ported (like to the 6.2 > series)??? In this case, a fairly severe bug was fixed by going "forward" > to the "less stable" series and the comment There won't be any Bugfix for 6.2.*. Lifetime for LO 6.2 is at the end. There hasn't be a special bugfix for this bug as for bug 123962. So there couldn't be backported anything to LO 6.2. Let us close this one as WORKSFORME, because the bug won't appear in LO 6.3 any more.
Yes! Close this bug, as it works for me!