Self-Devpt. Nuggets™

I build custom Excel-VB driven software used by a growing number of individuals and businesses within and outside Africa.

Over the past decade in particular, I have successfully tailored the solutions I offer to SUIT the local environment we have, in my part of the world (Africa). And I did it in a way that appeals to many results-focussed business users who are enthusiastic about using Information Technology to IMPROVE the way they work.

It is therefore only natural that such existing clients – and the prospective ones I approach – should wonder about the continuing relevance of the platform I use for developing and maintaining the solutions I provide them.

This matter has become even more important since the first version of Visual Studio Tools for Office (VSTO)/Visual Studio Tools for Applications (VSTA). The first version has since been improved upon – and continues to get better.

Discussions have raged among active members of the VBA community about how this new resource from Microsoft affects Visual Basic for applications (VBA) and its usefulness to end users.

Here’s my take on the whole matter…

For those who believe the "entry" of VSTO/VSTA" marked the end of VB for Excel, here’s some advice: Don’t count on it.

The debates have continued even as Microsoft continues to roll out newer/richer featured versions of the new platform.

One TRUTH that remains clear to all objective "viewers" is that except it wishes to commit financial suicide, Microsoft will continue to ensure VB for Excel functionality in newer versions of MS Excel it releases.

I can attest to this being true because the Hotel, Restaurant & Bar Manager software I built for a client was developed to run on MS Excel 2007 and higher versions. All I did was to ensure its backward compatibility with lower versions down to MS excel 2000.

The fact remains that many small businesses and departments in large corporations will continue to NEED the kinds of quick/easily developed and deployed solutions that VB for Excel allows.

Of course, with VSTA getting better, more use is likely to be made of it, but I believe it remains critical that POWER still be left in the hands of end users as has been the case with VBA if maximum user benefits are to be derived.

I say this because it is highly inconceivable that corporate IT departments will EVER have time to cater for different departments’ needs – in terms of developing rapid custom software solutions – on the scale that VB for Excel solutions allow.

I first wrote the original article on which this piece is based, back in April 2008 i.e. six years ago.

To arrive at the conclusions I stated in this piece, I tapped into my own experience based insights, and also reviewed discussion threads involving some prominent members of the VBA community.

They included professionals who have built custom Excel-VB driven software used by some of the world’s largest corporations, including Microsoft itself!

Today, in 2014, everything I said remains VERY relevant.

If you’d like to know more, I recommend you Google "Is VSTO/VSTA intended to replace VBA?"