https://bugs.documentfoundation.org/show_bug.cgi?id=162713

            Bug ID: 162713
           Summary: Date and time column do not use the correct format in
                    Base
           Product: LibreOffice
           Version: 24.8.0.3 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Base
          Assignee: [email protected]
          Reporter: [email protected]

Description:
I have an older Base application (8 years) with a window where date are
presented in a tabular form. Two colums are defined with format hh:mm:ss and
dd.mm.yyyy respectively- Every time when I open the form nn version 24.8.0.3.
the data are present with formats hh:mm and dd.mm.y respectively.

I can change this by clicking on the column header and choosing the correct
format. But the presentation of the time data change only when I select another
column. This is a minor subject. 

More serious is the behaviour of the data column. Changing the format to
dd.mm.yyy results in mm.dd.yyyy. The German format is ignored.

I can change the formats in the development mode. Saving the changes in the
dev-mode and in the main window of LibreOffice and then going back to the
working mode, everything is fine.

But closing LibreOffice ad restarting the application, all format changes are
lost.

My system: Windows 10, 64-bit, latest update

Steps to Reproduce:
1.See description
2.
3.

Actual Results:
Format changes of time and date colums are lost after restart LibreOffice

Expected Results:
Format changes of date and time fields showed be kept.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 24.8.0.3 (X86_64) / LibreOffice Community
Build ID: 0bdf1299c94fe897b119f97f3c613e9dca6be583
CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render:
Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to