Visforms, "Column checked_out can not be null"

Hello Thomas,

Thank you very much for listing the SQL statements.
What you added yourself are all the data tables.

I actually just forgot to mention them.
It's great that you thought of that yourself.

And yes, it's very likely that one data table would have been enough for the one affected form.
But why only one data table was affected is a little inexplicable to me.

Best wishes, Ingmar

Yes it's weird for me too. As Mr Spock would have said "It's not logical" I also see there is backuptables of the forms too. Maybe something there somehow?

Hello Thomas,

The '_save' backup tables have many matching fields that should also allow null.
The '_save' backup tables are used to save the original data record that the user creates by submitting the form.

The form data record in the data table can be edited and changed at any time.
When the form data record is changed for the first time, the original data record is copied to the backup data record.
It can be retrieved from there using the 'restore user inputs' function and written back to the data record table.

If, contrary to expectations, you have problems of the type 'can not be null' again when editing form data, you can run the corresponding SQL statements.

Best wishes, Ingmar

Addendum:
In Star Trek VI: The Undiscovered Country, 1991,
Nimoy’s Spock spoke:
"When you eliminate the impossible, whatever remains, however improbable, must be the truth."