https://issues.apache.org/ooo/show_bug.cgi?id=122264
Bug ID: 122264
Issue Type: DEFECT
Summary: Search for recorded information fails at start of
session
Classification: Application
Product: Base
Version: AOO 3.4.1
Hardware: PC
OS: Windows 7
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: code
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
