I have recently had to migrate an old Access Project (.ADP) to an Access .ACCDB front-end database, using a DSN file and Linked Tables to connect with a SQL Server database.
This all seems to work OK so far, but when I edit an Access Form text control box that is bound to a field in a SQL Server Table and leave it "blank", Access throws up a run-time error telling me NULLs are not permitted.
This is indeed the case - in my SQL Server Table definitions I have confirmed that NULLs are not allowed and hae a '' default, but I don't understand why an empty field in Access (or even several "space" characters) are being interpretted as NULL.
If I tab through "empty" controls in my Access Form, no problems are reported. It is only if I try to "blank out" a filled text box and leave it empty that the "NULLs" error appears.
I did not have this problem with my old Access .ADP front-end.
Can anyone tell me why Access is interpretting "blanks" as NULLs and being (presumably) rejected by the SQL Server database,
and how to work around it?