How do I validate null data now that isnull has gone?

  • Thread starter Thread starter anon
  • Start date Start date
A

anon

I am using Visual Basic.NET 2002 and ADO.NET and am a newbie after using
VB4/5/6 for ages.

I am used to vb6 where we had the isnull() function to check if something
was null so that something could be done about it.

Example:
text1.text=iif(not isnull(rs.fields(0)) , rs.fields(0), 0)
Hence:
Text1 is given the value of rs.fields(0) if it is not null, otherwise it
is populated with a zero.

I am importing data from another MDB file which unfortunately has null
entries in it, being both string and integer fields.
I have to assume that I have no means of getting to the source database to
edit it with MSAccess and therefore need to validate it at the point of
entry into the program.

I have tried to use not null, not nothing, and various other syntaxes and
have not come to any succesful conclusion.

Can anyone come up with the method I should employ to get around this
please...

Thanks in advance.

Terry
 
Back
Top