G
Guest
Hi,
I just installed Visual Studio 2005.
In VS 2003, if a field's NullValue in a data table is set to -1, I can
assign it -1 in code as NULL value.
But in VS 2005, look like the data table doesn't take -1 as NULL value
although property NullValue = -1. it takes it as a normal value and check
table relationship to see if it's in primary key table.
I saw in 2005 property DefaultValue is set to <DBNull>. I don't care this
property but <DBNull> make me think that 2005 may use <DBNull> as Null value
no matter what the NullValue is. NullValue is only used to return (get), not
for assign (set).
If it's the case, what's the easy way to fix it? Can I just modify some
property settings or I have to change my codes anywhere there is a -1
assignment?
Thanks.
Li
I just installed Visual Studio 2005.
In VS 2003, if a field's NullValue in a data table is set to -1, I can
assign it -1 in code as NULL value.
But in VS 2005, look like the data table doesn't take -1 as NULL value
although property NullValue = -1. it takes it as a normal value and check
table relationship to see if it's in primary key table.
I saw in 2005 property DefaultValue is set to <DBNull>. I don't care this
property but <DBNull> make me think that 2005 may use <DBNull> as Null value
no matter what the NullValue is. NullValue is only used to return (get), not
for assign (set).
If it's the case, what's the easy way to fix it? Can I just modify some
property settings or I have to change my codes anywhere there is a -1
assignment?
Thanks.
Li