The Weird and The Wonderful

Well, Order By is of some use, even in views. But it should ALWAYS be paired with a TOP(X). SELECT TOP 100 PERCENT * FROM Somewhere ORDER BY whatever is a true, classic, horror.

Maybe he was thinking of the 'String' theory! Yeah, I know, it's a groaner. Attempting to load signature... A NullSignatureException was unhandled. Message: "No signature exists"

Gary R. Wheeler wrote: ObjectServiceFactoryServiceObjectAutomationLinkFactoryServiceFactoryObjectMetaObjectBuilderFactory. You forgot "GoldProTeamEdition"... Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water

Back in school I once spent two days and several hours debugging a problem caused by an 'h' that was supposed to be a 'b', and vice versa. Software Zen: delete this;

I think it would be less misleading if the ReturnFalse function was instead named AbortAction or something closer to the intention. I think it is better practise to name a function or method for it's intended purpose or meaning than for what it literally does. The intention/meaning and what the method actually does usually are the same, but there can be subtle differences and occasionally vast differences such as in this case. Oh and a comment for the function would not go amiss either: //This function is used to suppress events such as onclick function AbortAction() { return false; }

Exactly! (and thanks for posting!) I was wondering how I could even declare app as a Crystal Report Application object to begin with. Turns out it works fine and was not the cause of our problems. The problem was corrected by using late binding on the Crystal App object. "Go forth into the source" - Neal Morse

Let me be the first to congratulate you. Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]

Ok I get it. Better to totally stuff it up once and then exclude that revision than watch it slowly get worse and worse. I remember the first time I bumped into this. Started work at a new place, committed some changes and about 10 minutes later, someone comes up and asks me to change options to tabs. 10 minutes!... damn code Nazis. :) "You get that on the big jobs."

A good candidate for that would be the data object itself. Just to take another example than simple validation: Let's say we have the common case that we need to store a password, which should be salted and hashed for security reasons. Why not put the method to do that into the data object? This way it can be ensured that the salting and hashing is done every time the password field of the data object is set. And this method can also be called to hash the string entered during login and then compare it to the value stored in the data object. This may be contrary to the dogma that data objects are supposed to be simple containers for the data only, but in object oriented design it makes sense when an object has methods or properties to validate its state or make changes to its state. I'm invincible, I can't be vinced

Honestly, no matter how bad or well written it is, all objective C code looks like a coding horror to me. But I suppose this looks worse then most.

don't forget to check that your current process owns the lock after setting it - another process may have locked it between you checking if its locked and you locking it

One free interwebs, you just won it! :) Jeroen De Dauw (blog | Twitter | Identi.ca)

Haha, I remember one government site. That entire site was developed in the local windows based PC and when they upload it to the linux server all the freaking path was absolute "C:/Program Files/PHP/WWW/....." Mentally disorder will do better work than that one

I hate when the boss is a complete idiot

The bad practice is failing to write the statement explicitly. Why change MONTH when it's meant to be 'month'? The shame is not using "SELECT B.[MONTH] + MONTH..." Yet, even that is minor.

How about?: protected void Page_Load(object sender, EventArgs e) { List Stuff = new List(); do { foreach (Node thing in Node.GetCurrent().Children) Stuff.Add(thing); } while (Stuff.Count < 100 && Stuff.Count > 0)) Stuff = ShuffleNodeList(Stuff); }

5 stars... that made me laugh.

:laugh:

I would say that not being able to use VS2010 until I installed the hotfix after installing SP1 is "important" This articles discusses it as well http://visualstudiomagazine.com/articles/2011/03/11/developers-react-to-visual-studio-2010-sp1.aspx[^] Also, I find it very frustrating that on a daily basis VS2010 runs out of memory and I to close and reopen my solutions. Also, there is still a known bug when queueing builds on build servers if you have more than one build server.

its a programming forum dude, even though its a shame