And here in the UK we had "bloody awful weather - start of the week day". It's not catchy, and it's not a holiday, but it's ours and we're going to guard this with glee.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
My blog | My articles | MoXAML PowerToys
True, but that Validate function is still easiest to read if it has multiple return false statements for each error check that fails and one final return true at the end if it passes all the tests. Regardless of where the error checking is, I always find it more readable to do it this way rather than massively nesting the multiple error checking to force the routine into only having a single exit point - the OP's original point. Judy
cp9876 wrote:
seems to be never
Really? Gee I must be sleeptyping again. :laugh:
Luc Pattyn [Forum Guidelines] [My Articles]
this weeks tips: - make Visual display line numbers: Tools/Options/TextEditor/... - show exceptions with ToString() to see all information - before you ask a question here, search CodeProject, then Google
Yes, but a man in a wheelchair is quite capable of finding the ramp up to the front door. ;)
BW
Quick to judge, quick to anger, slow to understand.
Ignorance and prejudice and fear walk hand in hand.
-- Neil Peart
Ed Gadziemski wrote:
But doesn't everyone who knows you eventually reach this point?
Probably, I'd ask someone but I'm not on speaking terms with them...
Matt Newman
Ok. Just got back to this now. We are using a single connection object that is opened at the start and then closed after performing all the inserts... My trace just shows many Audit Logon messages rather than connection open messages.