Created attachment 160287 [details] Open the database and have a look at the decimal-places of time in report Open the attached database. It contains one table with a field for a time and a flied for a timestamp. Both fields were filled with a value with 3 decimal places. It could be seen in the table. Open the form and see the content of the formatted fields at the top of the form. Showing decimal places of a time or a timestamp only works with a formatted field. The decimal places are shown. Close the form and execute the report. The decimal places of the timestamp are shown, the decimal places of the time where lost. Could be this never worked and has never been detected before, because the internal HSQLDB doesn't create TIME-fields with decimal places. It will only show decimal places with TIMESTAMP-fields and a special TIMESTAMP(6)-command. Why doesn't the Report Builder show the same content as a formatted field in the form? This buggy behavior appears under LO 6.4.4.1 on OpenSUSE 15.1 64bit rpm Linux.
You could solve this problem for Firebird by starting the report with a query: SELECT "table_time".*, CAST( "table_time"."Time" AS TIMESTAMP ) "TTime" FROM "table_time" If I change the type of the field to a timestamp in a query it will work ...
On pc Debian x86-64 with master sources updated today, I could reproduce this. I also noticed that in form or in report, when I open Format dialog, this format is never shown.
Dear Robert Großkopf, 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
Bug still present in Version: 7.2.6.2 / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded
Bug also present in Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 69f412459257398a7d779541dad95aa7227a5e74 CPU threads: 8; OS: Mac OS X 12.2.1; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded
Bug still exists on Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded