March 2017
-
More about ISEMPTY
I had much second thought about whether I should even blog this one. You know, it so profoundly belongs in the Duh! category that I have actually created the Duh! category specifically for this post. Now, fasten your seatbelt. I apologize for what you are about to see, but apparently people do write code as the example below.
-
When you just must COUNT, no matter what
I started with blogging about COUNT = 0 situation. Then I followed it with COUNT = 1. So, let’s do a COUNT = 2 today. No, no, I am just kidding, don’t worry 🙂 But I still have to do one more COUNT post, one that will cover all other COUNT situations. Believe it or not, sometimes you really, honestly, do need to perform an actual COUNT.
-
The “IF COUNT = 1” Conundrum
If you haven’t read my yesterday’s post , then do that first. Good. At this point you are extremely smart because you know that you should never use COUNT = 0 but should use ISEMPTY instead. However, what if: IF SomeTable.COUNT = 1 THEN DoSomething(); Well, if this is what you need, then that’s what you need.
-
Are there any records there?
It’s been a while that I haven’t blogged, and my queue grows inversely proportional to the amount of time I have available for blogging, so let me do a short series of easy stuff, simply to take it off the list. This is not about new features, crazy new tips and tricks or anything of the sort.