You know, I really like Access 2003 as an administrator's front-end to a SQL database that is principally backing-up a web site. It never made much sense to me to invest the extra time to wrap a bunch stuff up into ASP.NET to do trivial data edit tasks. I still feel that way but I just got burnt by it a bit.
Well, not just a bit: a three-state bit.
More Here...
Who: .NET and SQL Geeks in the Redmond/Bellevue/Seattle area.
What: World Famous Scoble's Geek Dinner
When: 2004-12-15T18:30:00-0800
Where: Crossroads Mall, Bellevue.
Why: We'll be hungry?
How: Just show. I'll be the fat guy in a Santa Hat NOT wearing a Red Suit.
On my current main project, I'm stuck writing a lot of code like:
if not(x is nothing) then
Yes, it's VB.NET. And, no, I don't have choices.
You know what I really want? A function that looks at a object of any type and if its Nothing, dbNull.Value or String.Empty, return False, otherwise, return True.
At least
if IsSomething(x) then
would be less boring to write over and over and over again.
And no, I'm not in the mood to argue semantics about what nothing really means, either... unless you are Kiri-kin-Tha.