Technically this error should not be happening, no matter the NotBlank property or not. Fields in Navision SQL can NOT be NULL. In Navision fields can be Blank, but Blank and NULL is not the same. So I really have no idea. But I would try solve it by trying to isolate the error. If it happens by all users, is it a "techncial" problem or what could it be?. Could it be related to the SQL database. Are you doing this "in production"?? What happens in your test environment when you do the same? Does it happen in a different company? What if you create another datatime field? Does the same then happen? Did you previously have a field with the same name in the same SQL table? Sorry for more questions than answers.
↧