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


Am 24.07.2012 13:34, Michael Crider wrote:
I have csv files generated from an SQL command-line utility that I am
trying to convert to dBase using the batch converter. If I open the csv
in LibreOffice, a default option is "Quoted fields as text", and if it
is saved as another filetype, those fields remain text, but when using
the batch converter it will bring all numbers in as numbers, even if
they are quoted. The command I am using is:
libreoffice --headless --invisible --convert-to dbf *.csv
I have the same results if I convert to other spreadsheet types. Is
there a way to tell the batch converter to convert "quoted fields as text"?



CSV is a database exchange format. dBase is a database in a directory. Why do you try to load csv into spreadsheets? Why csv at all? Probably you can connect Base to the database and use it directly. Base is a versatile tool to serve database data to office documents and it can be used to move data from one database type to another.


--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.