https://bugs.documentfoundation.org/show_bug.cgi?id=153331

            Bug ID: 153331
           Summary: Base Database files no longer working after update
           Product: LibreOffice
           Version: 7.4.5.1 release
          Hardware: All
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Base
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: lex...@yahoo.com

Description:
I tried to work with my database files today, and any time I enter information
into a form and try to move to the next one or to close or save it, I get this
error:  
Attempt to insert null into a non-nullable column: column: ID table: Inventory
Table in statement [INSERT INTO "Inventory Table" ( "Base
Cost","Brand","Description","List
Price","MSRP","Quantity","SOLD","Scent/Color","Sold for?") VALUES (
?,?,?,?,?,?,?,?,?)]

and I get this when I click on "More":  SQL Status: 23000
Error code: -10

Attempt to insert null into a non-nullable column: column: ID table: Inventory
Table in statement [INSERT INTO "Inventory Table" ( "Base
Cost","Brand","Description","List
Price","MSRP","Quantity","SOLD","Scent/Color","Sold for?") VALUES (
?,?,?,?,?,?,?,?,?)]

Can you tell me why it's suddenly doing this? I have several different copies
of this file on several different computers and every file is doing this.
Restarting in safe mode does not solve the problem

Steps to Reproduce:
1.enter information into form 
2.try to exit or save entry
3.

Actual Results:
I received the above error message and the information is not being saved at
all.

Expected Results:
the information should be saved and I move on to the next entry form


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.4.5.1 (x64) / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 4; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to