Problem description: In the tables, then field format, the format code resets from time to time. This appear to be especially prevalent when making changes to the database or following a the crashing of the database. Steps to reproduce: 1. Create table. Then in design view add some fields. Choose field type "decimal". 2. Go to format example and select e.g. #,##0.00. 3. Save changes, then close, then open database. 4. Repeat. Make more changes. Add table. Add fields. Crash system if possible. 5. Eventually somehow the formats are reset. I could not pinpoint exactly what triggers this format being reset. Current behavior: Table field formatting resets/ is lost once in a while. Expected behavior: Table field formatting being permanent. Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7
*** Bug 44307 has been marked as a duplicate of this bug. ***
*** Bug 44308 has been marked as a duplicate of this bug. ***
Thanks for bugreport Please, attach two databases: produced in step 3 and produced in step 5
Created attachment 61601 [details] original data
Created attachment 61602 [details] attempting to replicate error
Dear sasha, Sorry for the late response. I've tried to duplicate the error but without success. (I'm attaching the databases so you can see what I'm trying to do, but otherwise you can ignore them). I'll continue testing and see what exactly might be causing the problem. Thank you.
Thanks for attachments. May be it fixed in 3.5.3
Hi Jorge, exists your problem still using LO 3.6.0 or 3.6.1 RC1?
(In reply to comment #8) > Hi Jorge, > > exists your problem still using LO 3.6.0 or 3.6.1 RC1? I have now just installed LibreOffice 3.6.0: - I continue to loose the formatting on the tables on my existing database that I use at work everyday. However this database is almost a year old and has gone through x100s of edits, so there might be some "bug" that I'm carrying with it. - I'm trying to replicate the error on a fresh test database, but so far I'm unsuccessful. I'll continue testing for a while and see if I manage to "break" the new test database.
(In reply to comment #0) > Steps to reproduce: I don´t understand what Jorge want to say. Reproducing the steps all works fine (OS: Windows XP; LO 3.6.0) @Jorge: 1) List the single steps - e.g. "create table": click on "Create Table in Desing View..." etc. 2) Please create screenshot(s) @Robert: Have you time to look at this bugreport? Can you reproduce what Jorge means.
(In reply to comment #10) > (In reply to comment #0) > > Steps to reproduce: > > I don´t understand what Jorge want to say. > Reproducing the steps all works fine (OS: Windows XP; LO 3.6.0) > > @Jorge: > 1) List the single steps - e.g. "create table": click on "Create Table in > Desing View..." etc. > 2) Please create screenshot(s) Table formatting works fine... But *sometimes* this table formatting is lost. I'm working with numbers formatted with "Thousands separator" box checked in the Field Format dialog and also right alignment. Everything will look fine, I double check, close, open, close and open again the table and also the database... still everything ok. Then I'll close and open the database once more and voila! Formatting now is lost: numbers no longer have the thousands separator, and sometimes the alignment has reverted to the left default. Again... this a rather frequent occurrence on my "old" database that I use at work every day and I've edited hundred of times. However I'm trying to replicate (unsuccessfully) the problem with a fresh database. (Maybe I've got something on my big work database that's causing the problem... maybe legacy issue/ bug/ corruption... maybe it's some feature that I'm using on this database and not on the new test database such as macros, queries, reports... ????) ... Meanwhile I will continue to attempt to replicate error with new test database...
Hi Jorge, how does it look: can you reproduce the behavior with a new Base-file still? Can it be that the problem exists only with your "old" Base-file?
Dear all, Thank you for all your given support. I have decided to close the bug as I'm simply unable to replicate the error outside of my "old" database. (Maybe my "old" database odb file that goes back a number of versions and I use everyday and have edited 100s of times might have gotten corrupted/ carries some legacy bug/ or who knows what...) So: for now I'm closing this "bug". Thank you all!
Thanks for additional testing Due to last comment, changing status to WorksForMe If problem will reproduced from scratch, please, change status to Reopened