Description: Version: 6.0.2.1 (x64) Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 8; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group In Form View of database notice the bottom left corner, This is where the information "Record" (value) of (value) is placed example: Record 150 of 150. The bug appears when a new record is added and increments the total number of records. as an example if record 151 is added, it correctly displays as 150 in the box next to the word Record. However, in the area to the right of the word "of", the 151 overwrites but does not erase the previous number of 150. The result is that the "1" in 151, superimposes itself on the "0" of 150. Steps to Reproduce: 1.Create a form with the wizard in Base, import a table with over 100 records. 2. Observe the lower left corner showing magnifying glass and Record___ of ___ 3. Add a new record in form view, observe the overwrite error in the "of____" 4. If the window is minimized and maximized, the overwrite error is resolved. 5. If you continue to add records without minimizing the window the subsequent total number of records "of___ will overlay the previous "of____ value, creating a mish mash. Actual Results: 1.Create a form with the wizard in Base, import a table with over 100 records. 2. Observe the lower left corner showing magnifying glass and Record___ of ___ 3. Add a new record in form view, observe the overwrite error in the "of____" 4. If the window is minimized and maximized, the overwrite error is resolved. 5. If you continue to add records without minimizing the window the subsequent total number of records "of___ will overlay the previous "of____ value, creating a mish mash. Expected Results: The program continues to run, the file is not corrupted. Reproducible: Always User Profile Reset: No Additional Info: In this situation, the total number of records (the YYY region) in the Record XXX of YYY area in the lower left screen should be refreshed by erasing and then posting the new value. As an example in Record 151 of 151, the 1 in 151 is superimposed on the 0 of 150, the previous total "of" record. The combined overlay of 151 over 150 makes the last digit unintelligible.
Maybe it is a windows situation. Checking 6.2Alpha0 and Ubuntu 18.04 could not reproduce this with 3 different forms, with grid contorls, from 3 different databases with record counts from less then 100 to over 2,000.
No repro with: Version: 6.2.0.0.alpha0+ Build ID: ab3e7a234fb6e55274159952743d6c937c7c3f7c CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group threaded Using a form containing a grid control. The record count displays correctly and is not overwritten. Seems to be a Windows only problem ? @mitchell : you mention the affected version as 6.0.2 in your report, yet have selected 6.2 alpha as the affected version in the bugzilla form. If you are really using 6.0.2, then you could try upgrading to the latest 6.0.x version to see if there is any difference, if not please report back here. Additionally, you do no specify which form control object contains the record count. Bot Drew and I have tested with a grid control, but perhaps you mean the more general record counter form object that is displayed at the bottom of the window ? Setting to NEEDINFO.
Separate confirmation would seem to be have been reported through bug 118791 - affects both Linux and Windows
*** Bug 118791 has been marked as a duplicate of this bug. ***
(In reply to Alex Thurgood from comment #4) > Separate confirmation would seem to be have been reported through bug 118791 > - affects both Linux and Windows NEW, then. Did this work in an older version? https://wiki.documentfoundation.org/QA/BugTriage#Step_7:_Regression_Testing
For some reason I got a direct email response from the reporter: > I have only worked with Base recently and have no previous experience with it in older versions of Libre Office. I now have two database files and the counting error occurs in form view in each case. I believe the problem more likely to be program code related than data file corruption. Would still be interesting, if the affected people could install older versions in parallel and test.
*** Bug 118886 has been marked as a duplicate of this bug. ***
Dear mitchell93210, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear mitchell93210, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear mitchell93210, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug