Apache OpenOffice (AOO) Bugzilla – Issue 122264
'Find record' for existing contents fails at start of session
Last modified: 2017-05-20 09:36:03 UTC
Along the past years I have implemented with Open Office Base a database with several data tables, queries, forms and macros for personal use. It has several thousand registers and works fine. I have updated just recently to version 3.4 of Open Office, having then found the following problem. When the main form of the database is opened for the first time, one of the elements of the form navigation toolbar shows information about the present status of the application and the database, saying in my case: 'Register 1 of 40*'. If in this situation a search is performed for some datum which surely exists in some register of the database, but which is not included in this initial set, the operation ends with a message of *No registers found*. This is very misleading because it implies that the required information does not exist in the whole database, which is false. Just repeating the search does not change the situation at all. After much frustration I noticed that the search behaved normally if performed after one had moved around in the database so that the registers containing the requested information were included in the bigger set then reported at the form navigation toolbar. Following this hunch I have finally found what seems to be the only sure way to circumvent the problem: after opening the form, one has to move straight to the last record of the database by pressing the button 'last record' of the same navigation toolbar. After this *priming*, the rest of the operations related to the database apparently behave as they should. I had not noticed this problem using OOffice 3.3 for many years, although I can not swear that it did not exist there.
Further experience with OOBase 3.4.1 confirms that all forms of any database are affected by this problem at the moment of their opening. I reported the fault in the case when the searched item was not contained in the first partial set of registers adressed by OOBase. If the information exists in such a set, it is regularly found but *Find next* reproduces the problem by not jumping over it if a new instance of the item is not there. For the moment I have *patched* the inconveniences by attaching the following macro to the opening event of every form in the database: Sub WalkForm( oEvent as object ) ' get a handle to the present form dim thisForm as object thisForm = oEvent.Source ' jump to its last register thisForm.last() ' and back to the first thisForm.first() end sub
Reproducible with server installation of "AOO 3.4.1 – German UI / German locale [AOO341m1(Build:9593) - Rev.1372282]" on WIN7 Home Premium (64bit)", own separate user profile. 'Find Record' in a record number 700 or so ends with error message "No records corresponding to your data found", although data does exist WFM with "AOO 4.0.0-Dev – English UI / German locale [AOO400m2(Build:9701) - Rev. 1495357 Rev.1495357 2013-06-23]" on WIN7 Home Premium (64bit)", Common 4.0-dev User Profile Seems the problem has been fixed. @reporter: Please feel free to reopen this issue if you find out that the problem still exists in the latest release of AOO or AOO 4.0-dev
I wonder what tests I did for Comment 2, the problem still seems reproducible for me with "AOO 4.1.0-Dev – English UI / German locale - [AOO410m1(Build:9750) - Rev. 1521488 - 2013-09-11]" on German WIN7 Home Premium (64bit)", own separate user profile. That's not unexpected because "Bug 22831 - Scroll Slider scrolling of large database tables stops at record 40" still is unfixed for Rev. 1521488. I will check again.
Still Reproducible with "AOO 4.1.0-Dev – English UI / German locale - [AOO410m1(Build:9750) - Rev. 1523968 - 2013-09-18]" on German WIN7 Home Premium (64bit)", own separate user profile I think I made a mistake during my tests for Comment 2, the result was nonsense. This one is a DUP of "Bug 22831 - Scroll Slider scrolling of large database tables stops at record 40" *** This issue has been marked as a duplicate of issue 22831 ***