>Hi,
>
>Yesterday, a customer had to restore one table in the SQL Server DB. The reason was that they made a mistake, updated multiple rows and it was wrong. So, the DBA restored the table from the backup.
>
>Now, whenever they (any user) try to add a row/record to this table, an error comes up that the sql server cannot insert the value NULL into a column "so_and_so". And if I change the column to allow null, the error goes to the next column that does not allow NULLs. I checked that there are many columns that do not allow nulls and it worked before. Now it failed.
>The application is using CursorAdapter.
>The application has not been changed.
>
>Any suggestions?
>
>TIA
You should have DEFAULT values for the columns that does not allow nulls (unless of course they should be filled by the application)
The other way is to set DEFAULT values in your CA CursorSchema property.
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.