5am start. 40 other people all doing the same. Force yourself out of a warmish bed to a very cold Alpine hut. Bag was packed the evening before so it’s just extra clothes on then downstairs for breakfast. Cereal and milk, bread and jam and some hot but tasteless black water, or coffee, as they were calling it. Sense of trepidation about what lay ahead. On paper it was a 1,300m ascent to 4,020m, but this was via rock ridge and a narrow snow ridge. Surely it couldn’t be too bad?

Holidays this year were a week in the Saas Valley in the Swiss Alps in Switzerland. It was my Dad’s idea, and when he suggested I join him and family friend Brian and mountain leader Mike for some climbing 4000m mountains, I thought why not? Bonding time with the old man, how bad could it be? Well, I made the mistake of checking out some video before going and was soon wondering what I’d let myself in for. I then found the blog of a group who had just got back from a trip doing moreorless the same thing as we were planning, I don’t think it put me at ease in the slightest. Don’t get me wrong, I’m probably above average fitness and fear levels, but still, photos of the Weismies traverse certainly had me wondering about my ability. After scavenging as much gear as possible, as well as a shiny pair of new Scarpa Cumbre boots and some Grivel 12 crampons, I thought I was all set. The one thing that had been reiterated to me over and over again - travel light! Whatever’s in your bag, you have to carry, so if you don’t need it, don’t take it. So with literally two pairs of pants, two pairs of socks, some emergency food and zero luxuries (i.e., no iPad) we were set to leave Guernsey for Geneva.

The electric window switches on my 2001 6n2 VW Polo GTi recently had always been a bit hit and miss - they’d work about 75% of the time, then one day, they just stopped working completely. It’s a common problem on these cars - and actually, I’d wager it doesn’t just afflict Polos, probably any of the Golf/Seats/Skodas etc. that use the similar components. The problem in my instance was not electrical (well not really) - that is the windows and the switches themselves were fine, the problem was that there was a build-up of “green corrosion” on the electrical contacts - a side effect of the oxidation of the soft metals used in the contacts. The end result is that the green sucks away the power running through the switch, so enough doesn’t get through the circuit, and hence the switches don’t work.

I’ve been working with the BDC and a proprietary CRM system to bring data about sales history into SharePoint. I’ve been using the basic BDC tool - Business Data Catalog Definition Editor - that is bundled with the SharePoint SDK. It’s very basic, and there are one or two commercial products out there, but it just about does enough, and is free, after all. It enables you to define the entities, relationships and methods, and test them, within the tool. The error reporting is moderate - you’re informed about the major issues, but, some errors only appear when you’ve imported the ADF and are actually working within the SharePoint environment.

The Business Data Catalog (BDC) in SharePoint is a superb way of hooking up virtually any disparate system to SharePoint 2007. By defining the connection in to the system, you can expose any part of the system to SharePoint, and harness some of SharePoint’s real power - for example, its powerful search capabilities. Once you’ve created your connection (your Line Of Business [LOB] system), you can attach BDC columns to any list (e.g., document library) and you can, for example, have a document with a reference to your other system, so that you can permanently associate extra data to your document, without having to reproduce the information in SharePoint and create unnecessary duplication.

Using the BDC is beyond the scope of this post, but I’d like to cover an issue that I recently encountered when trying to work with the BDC and a document library. I had a fairly simple Visual Studio 2008 workflow that ran when a new item was created in the document library.

Any SharePoint developer will have to work with SharePoint Features at some point. Features are a great way to extend the core functionality of MOSS - in Web 2.0 speak, think of them as “plugins” and you’ll understand why they’re useful. Features can take a variety of forms - workflows being one of them. I’ve discussed in the past the usefulness of SharePoint Designer for workflow creation and eventually you’ll need to move to Visual Studio. Features (and workflows) can be designed directly in Visual Studio - support was added in 2005, but its support is further extended in 2008 - Visual Studio will generate all the required bits you need to actually get the workflow ready to be deployed to your SharePoint environment and gives you the all important debugging and code step through stuff. There’s a nice guide to the basics of workflow and Visual Studio.

SharePoint Designer 2007 is a useful tool for performing quick tasks in your SharePoint environment. It’s moreorless Frontpage on steroids, but it’s designed to interact directly with SharePoint installations. I’ve used it almost exclusively to create simple workflows - simple being the operative word. And what’s more, it’s now free! You’ll need the likes of Visual Studio to do anything complex, but for every day use where you don’t want to worry about packaging up solutions and features and getting involved with stsadm, SharePoint Designer definitely has its place.

I recently updated the firmware on my Alesis DM5. The update has been around for ages, but I didn’t have the interface between the DM5 and my PC. I was in limbo about it all - I was looking at the Midiman Midisport 2×2 but I felt a bit aggrieved spending some thirty quid on something I was likely to use once. (I already have a M-Audio Pro 44 keyboard that hooks the kit in to my PC.) I finally bit the bullet and trusty old eBay turns up a nice and cheap USB Midi interface - I was dubious about something for £0.98 - whether it would really work.

I needed to update our installation of SQL Server 2008 to include Integration Services so that maintenance plans would run. I have local admin privilege on the machine, but as with most Microsoft related installation tasks, you routinely get so far through the process and you’re hit with the SeSecurityPrivilege error - that is, you don’t have some permission or other. The installation process goes wrong and you have to cancel out of the whole process in order to restart it with an account that has the privilege.

Way back when, I thought an alarm on my motorbike was a good idea. My bike had just been vandalised by a drunk and I had become a bit paranoid. And, in fairness, since having it, my bike was never stolen. Admittedly, I’m not certain there were actually any attempts to steal it. The times that the alarm did get triggered was always me, or an ant looking at it and setting off the motion detector, and even on those occasions, any passers-by in the vicinity barely gave it a glance before moving on and ignoring the apparent attempted theft of my bike. Had I been trying to steal my bike, then I doubt the alarm would have done much to prevent it. Seems to me that alarms are pretty ineffective nowadays. Moreover, I can think of at least one easy way to completely disable it with very little fuss.

So when I recently had to replace my battery again due to its inability to maintain a charge - no doubt caused by the permanent drain that the alarm system puts on it - enough was enough, the thing was coming out. It was surprisingly easy to do, which made me wonder about its status as Thatcham approved and all that. It took the installer quite a few hours to put in - he did do a proper job - but I’d say it took me around 20 minutes to get it out. Not something you’d do on the side of a road in order to nick it, but still, surprisingly easy. And to think I paid around £400 at the time.

This isn’t supposed to be step by step instructions and I won’t describe how to dismantle your bike or get at the particular pieces - if you can’t work out that much on your own, you probably shouldn’t be doing this. And needless to say, but it needs to be said, this is what I had to do to my own CBR600… no guarantees it’ll work for your bike or be the same or anything. And I’m by no means an electrician. So if you permanently immobilise your bike - it ain’t my fault! And note that my alarm was functional but I had taken a rather unconventional route to completely disable the bike before I did this (took out the main fuse for the bike) - so the alarm actually wasn’t alive.