As I posted last week [http://codebetter.com/blogs/john.papa/archive/2005/06/07/64248.aspx], I got up a new iPod mini [http://store.apple.com/1-800-MY-APPLE/WebObjects/AppleStore.woa/70703/wo/e27TQK9bYtLU25UWo552kIaHoMA/1.0.0.11.1.0.6.9.1.1.1.1.1.0.0.1.0] for running and light soccer drills. It was

Enterprise Library [http://www.microsoft.com/practices] <P>There are some really good webcasts [http://www.pnplive.com/] on the different Enterprise Library Application Blocks [http://www.pnplive.com/]. You can download the slides, watch the video and grab some hands on code samples here [h

I’ve recently had a flurry of email asking how to navigate up to a grandparent table using ADO.NET. Assuming that it is not preferable to export all of the data to Xml and use an XPath, ADO.NET offers a few other ADO.NET based solutions. One solution is to use expression based columns. (If you want

I’ve been using BlogJet [http://blogjet.com/] for a few weeks now to post to my blog and while it has not overwhelmed me, it has proven to be a useful tool. Here are some quick observations that I have made regarding the pros and cons that are important to me: Pros: * It is nice to be able to pos

OK, so this isn’t rocket science, but then again some of the best things are the simplest. You can do a lot with the information_schema views in SQL Server. Here is a short stored procedure that you can use to find: * a table by its full name * a table by partial name * a column by its full