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


Windows 7 64 bit, Version: 6.2.3.2 (x64)

I have two databases.

Both have "ID" defined as the first field in the databases.

The first database is an import of text files that is unregistered. I believe it is Firebird, but do not know how to confirm this. The header to the text file has "ID" in the first line, first position and all its fields are blank.

Example:

ID;Model;Tube;Position;Date;Time;Ions;Select;Series;Settings
;1-1612-0023-192;1-1617-0009-1759;1.1;2019-05-14;3:32:00 PM;  503075;0;135;100

"ID" field was defined as "Text [ VARCHAR ]" automatically at Import and does not define "ID" as a key field.

The second database is firebird registered.

"ID" is defined as "Integer [ INTEGER ]".

When I want to append a Table from database one to database two, I get the message "No corresponding column type could be found for column 'ID'."

It does not let me skip this warning and move to the next screen where I would usually uncheck the field and allow automatic key to be filled in second database.

Any suggestions welcome.

Paul


--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

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.