Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

ubuntu 12.04

While fooling with mail merge, I decided to clean up my databases... I deleted them all and recreated the one I needed with a new name. That was a major mistake from which I was unable to recover, as now my fields don't match the database. At the same time, I added a few fields, one of which was a currency field. Currency comes with a comma as the thousands seperator. Which meant I could no longer use commas as my seperator in my CSV file. So, I saved it as a tab seperated file. So far, so good.

While converting all of the fields to use the new database, LO crashed (nothing new, it crashes about every 5 minutes). Because of these constant crashes I save each and every time I make just about any change whatsoever. I was nearly done with my changes.

The difference this time is that, it goes through the recovery process - and then crashes again. It's done this before, but typically a second restart is enough to get it past the problem, it recovers various files - fails to recover others that no longer exist - and then all is well and I continue my journey. This time, no amount of restarting LO will get it to stop crashing.

Any suggestions?

Thank you in advance.

- Andrew

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.