One other consideration though outside your stated requirements might be a Source Control tool such as Source Safe (Team Foundation Server) or SVN or even a local to your LAN...

Oops on my part, this is the code I've been 'working' on am I looking at the wrong thing?

strInput = <a string that is the parameter for my stored...

See if this helps:

If cmdObj.State = 1 Then

With cmdObj

.blah ...

End With

Else

'the connection is not open, try opening a new connection

...

http://rory.streetfamily.info/PermaLink,guid,11745f49-4608-408b-b112-bef88e857b6f.aspx

Could you be having the same issue as Rory, the connection is being auto closed on you?

Not enough information to help. What does your INSERT string look like? Is there just a single TABLE or is some sort of JOIN to another TABLE involved?

I wonder if a CLR function would be worth considering here? .NET includes the System.Globalization.TextInfo.ToTitleCase() function which seems to do a pretty good job getting things properly capitalized. Not perfect...

Miles, seriously this did not give you a hint: " ;<) " ?

Sorry if teasing the DBA crowd here offended you, it was not intended that way but...

This can really reach out to bite you when dates are involved, again sort of obvious but so easy to forget/overlook

The entire article could have more accurately been written in a single sentence:

"Assume developers literally are smarter then you otherwise they would have settled for being a mere DBA" ;<)

Sorry...

Thanks, I have almost never used this tool so your article was particularly informative.

The good news from those of us missing SSC newsletter, you know that they are in fact being read and thus missed when absent

Just a note SSRS2012 writes xlsx files about 1 Million rows. I know does not help with your older version but one more reason to upgrade

<begin>

Dim strRecip As String

Dim strTo() As String = recipients.Split(";")

For Each strRecip In strTo

MailMsg.To.Add(New MailAddress(strRecip))

Next

Instead of looping thru the array have...

I would imagine this has never been fixed (dates to 2001)

http://support.microsoft.com/kb/223180

Oh, I think arrogance is exactly the right term, it is arrogant to assume 'you' know better than I do about my network and my security. I can certainly understand...