This got me thinking about the nature of upgrades lately. Did you know, for example, that Microsoft is slated to release some 24 new or upgraded software titles through the end of this year? All in addition to the myriad applications, servers, utilities, etc. it already offers. Some are getting all sorts of attention (can you say Windows Server .Net, or is it Windows .Net Server, no, wait, Windows 2003 Server -- oh, you know what I'm talking about!), while others just kind of happen.

For instance, if you've developed, installed or supported a Visual Basic application that involves database connectivity -- in other words, just about anything written in VB -- you most certainly have encountered Microsoft Data Access Components (MDAC). Quick, what is the latest MDAC version: 2.5? 2.6? 2.7? Will an app requiring MDAC 2.5 work with MDAC 2.6? Which version of MDAC gets installed as part of an SQL 2000 install? With Office 2000?

Let's not just pick on Microsoft. Do you support Cisco routers or switches? Then you've had to deal with major and minor IOS versions, and their various flavors (switches vs. routers vs. firewalls, etc.). Or what about Netscreen and their ScreenOS? We've got a Net 5 at one of our home offices running version 3.0.3r5.0, and another one running 3.0.0r3.0. There's also a version 4 out there. Since we're not having any problems with either of these units we are hesitant to upgrade them. But then we have to also consider what Netscreen is officially supporting.

It is becoming increasingly difficult to keep up with all the software and hardware changes out there. As IT professionals we are pretty much at the mercy of the Microsofts, Ciscos and Netscreens of the world. Even so, there are some things we can do to help alleviate all the version headaches we are faced with:

1) Press for Business Solutions - Not Just Technology: Did all those folks who upgraded to Office XP really need to do so? While there's always situations where upgrading is the best approach (as was the case for the client I mentioned earlier), sometimes, it's just an excuse -- or worse, there's the "We need the latest version because it has this cool new feature" strategy. That's where my next tip comes in:

2) Educate the Users: Almost all of my clients wanted to upgrade to Office XP when it came out just because it came out, simply because it was the latest version. I was able to dissuade them by knowing how they used Office.

3) Take It Directly to the Vendors: Yes, Microsoft and Cisco are huge companies, but as a group we are hugely influential over the use of their technologies, and they should listen to us. For starters, don't underestimate the value of simply trying: Send an e-mail to the appropriate person and you'll be surprised at what can happen. For a larger voice (or for help trying to figure out who to send that e-mail to), get involved with other IT pros in your area through user groups, etc. It's amazing what you can find out when you schmooze with your peers, and you might get to know some of the folks at the local branch offices of various software and hardware companies.

This issue is much more complicated than what I've touched on in this column. For one, there are good reasons to upgrade. Vendor support is critical in many situations; sometimes you need to upgrade just to ensure that support is available. And if you make all or part of your living by selling software, no one can fault you for wanting to upgrade your clients. And we've all faced the opposite situation as well: The client who needs the upgrade who just doesn't want to pay for it!

So while there are many other factors to be considered -- and we IT pros already have much on our plates as it is --- with a little effort on our part, maybe we can do something to ease those upgrade blues.

What are your upgrade pet-peeves? Post your thoughts below!