Visual Basic 2005 Professional Edition:
I have an SQL database table that includes a BirthDate field. I would like to have this field as optional when adding a record, but, SQL insists on throwing an exception if the field is null.
Date field cannot be null!
Hot Topic
- SQL Server 2005 CTP Release Candidate Sept - unexpected failure during setup wizard
- Programmatically set position of report items
- SP_SETAPPROLE - Get Sql Err Message 15422 when activating application role
- Print Preview on Client side
- Online Data Transform
- Problem with source from Books Online - Application.LoadPackage
- Dynamic Login & User Creation
- HOW TO DEPLOY A PROJECT TO REMOTE SERVER(starve for)
- SSRS Question?
- Remote Connection problem on MS SQL 2000
SQL Server
- Visual Studio 2005 The remote connection to the device has been lost. Please verify the device connection and restart debugging.
- Changing data types of a variable in an expression
- How do I consume a DataReader Destination in VB.Net?
- How to Delete Files on Maintenance Plan
- Transferring Records from a table to multiple files
- SQL Mobile query hangs PPC 2003 device
- Regarding Structured storage file.
- HowTo Union a given query across n duplicate databases
- Is this possible?
- Encryption and recovery on standby machine
Date field cannot be null!
chale
I went into DataSetDesigner and in Properties I set AllowDbNull to True.
But, when I tried to change the NullValue property from "Throw Exception" to "Empty" or "Nothing" (there are only 3 choices) it said "For columns not defined as System.String, the only valid value is (Throw exception)".
mfsumption
The following exception occurred in the DataGridView:
System.Data.NoNullAllowedException: Column 'BirthDate' does not allow nulls
I set 'AllowDbNull' to True in the properties field of the DataSet Designer, replied 'Yes' to 'Save Changes', but, when I go back in, 'AllowDbNull' is back to False.
Vnsmith5
Given that you've just allowed nulls, the value of the NullValue property is irrelevant, as the exception should never be raised.
Jim Reyne
With this it looks like your table design has the field set not to allow nulls. You will have to alter the table definition to allow nulls for that field. This can be done in raw tsql, or using the table design views in either of the management studio tools.
FabrizioC
ok - I've done some research on this (I'm a SQL guy, not a VS guy) and it looks like there may be a bug in the Dataset Designer for non-string columns. I found what looks like a workaround here: http://www.codeproject.com/useritems/Bug_fixed_in_DataDesigner.asp
Hope this helps