Hey again,
In C#, I think you'd just check against null, e.g.:
if (Count==null)...
In VB, I think null handling goes something more like:
If Not IsDbNull Count Then
I'm not completely certain, but maybe look a bit more closely at IsDbNull
and DbNull.
Also, it looks like you've got a viable solution. You'll get different
schools of thought, but generally error-trapping is less efficient than
testing for a likely error. Rather than using a try...catch to handle
errors, you may want to consider checking explicitly for a null rather than
trapping for the exception.
HTH,
John
> For anyone interested, I fixed my problem with a little error trapping i
> found. Here is the example:
[quoted text clipped - 61 lines]
> > > easiest
> > > > way??
PCL - 28 Oct 2004 19:23 GMT
Thank You for your input - the error trapping seems to do the trick. I wasnt
able to get the synatx right for checking for null - i guess i could put it
in the stored procedure and it wouldnt be an issue. Thanx for your help!
> Hey again,
>
[quoted text clipped - 89 lines]
> > > > easiest
> > > > > way??