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

Hi Alexander and all:

        Thank you for your clear explanation. If I understood you well, this
happen when we predefined the table in Base that we think that we will
need. But when I have needed do it, I didn't make the table, I only use
connect option (when start BASE), with a .db (spreadsheet -.ods-) that I
have in my file directory. I think that in this way BASE create the
table with the characteristic of the origin (.ods file).


Jorge Rodríguez

El jue, 17-03-2016 a las 16:35 +0100, Alexander Thurgood escribió:
Le 17/03/2016 16:08, jorge a écrit :

Hi Jorge,

    I suggest to you to open the .CSV file with CALC. Then save it as .ODS.
Finally, import from BASE the .ODS file.

The import wizard from Calc to Base is not perfect, so unless one is
absolutely sure that the data in your CSV or Calc file exactly matches
the definition of the fields in the table, then one should expect either
import errors or failure. Particular things to watch out for :

- date / time / datetime representations
- text values over integers
- null fields
- values intended to be used in an autoincrement field
- boolean values
- memo fields
- unsigned INT field values
- zero-fill values

etc, etc



Jorge Rodríguez

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.