Seems like I guessed wrong twice. The problem that you have has
to do with adding a field that is NOT NULL. When you add a field to a
table, it has no values until entries are made. So, selecting "Yes" for
Entry Required causes the error.
Create the field with "NO" selected for "Entry Required." Enter
the appropriate data making sure all the rows of the table have an entry
for it. Now edit the table by setting "Entry Required" to Yes.
This is my first time using LibreOffice Base and in case I'm not very clear
... I haven't programmed anything in almost 15 years so this is a bit of a
transition for an old lady.
I'm creating a table and I want a field to be of type Integer and Not Null.
(Note: I already have another field in the same table that is with the same
configuration, ie Integer/Not Null, and I'm editing an existing table to add
I keep getting the error message:
Error while saving the table design
Column constraints are not acceptable in statement [ALTER TABLE "Companion
Subspecies" ADD "Help Type" INTEGER NOT NULL]
Could someone kindly point me in the right direction to correct my problem?
View this message in context: http://nabble.documentfoundation.org/Integer-Not-Null-tp3990551.html
Sent from the Users mailing list archive at Nabble.com.
For unsubscribe instructions e-mail to: email@example.com
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
Impressum (Legal Info)
: 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