argument-2

A: “Microsoft Access sucks.  It is the bane of enterprise technology and an enormously expensive impediment to organizational agility, and progress.”

B: “Why?  I happen to like Access.  What’s wrong with it?”

A: “What versions do you support?”

B: “2007, 2010 and some 2013.”

A: “Why not just one version?”

B: “Because some of the apps haven’t been upgraded yet.”

A: “Why not?”

B: “Because it takes time and resources.  And we’re short-staffed already.  Also, some of the code was written by people no longer employed here, so we don’t want to upset the apple cart.”

A: “So you have to maintain Office 2007, and 2010, or at least one of them, with some additional ‘runtime’ components to support them.  When will you move to Office 2016?”

B: “Not for a long, long, long time.”

A: “So you’re stuck on which version?”

B: “Office 2010, with 2007 runtimes.”

A: “Supporting multiple versions, components and having to educate your help desk staff on the configurations and ramifications, that has to add some time and cost.”

B: “Yes.  But it works.”

A: “And when you’re asked to migrate to Office 2013 or 2016, what then?”

B: “We will insist that management hire additional personnel to help port the older apps to the newer platform.”

A: “More cost.”

B: “Yes.”

A: “Then, even after migrating the code to 2016, when 2018 comes out, you have to do that work all over again.”

B: “Yes.”

A: “So, why not move the data into SQL Server, and move the UI into VS.net or a web front end?”

B: “Too expensive.”

A: “SQL Express will likely provide more than enough support for your apps, and it’s free.  VS.net comes in a free version with plenty of data and UI development tools available.  Even Notepad can be used to build ASP or PHP apps.”

B: “That would require training.”

A: “Training is free online.  It’s called Google and Youtube.  And TechNet has plenty of free resources as well, not to mention all the non-Microsoft web sites out there.”

B: “But what happens when I need to upgrade from SQL Express 2014 to 2016?”

A: “You upgrade the database or just move the data to a newer instance. Schema is schema.”

B: “What about when I need to update VS.net?”

A: “You install the upgrade, open the solution or project and continue working.”

B: “No code porting required?”

A: “No code porting required.”

B: (silence.  sweating profusely)

A: (hands towel and a shot glass filled with some amber colored alcoholic beverage)

B: (swallows. inhales. exhales) “Thanks!”

A: “And… nothing left to stop you from keeping current on your Office installations.”

B: (reaches for tissue box) “So, I need to think about this for a bit…”

A: “Microsoft Access sucks.  It is the bane of technology and an enormously expensive impediment to enterprise flexibility, and progress.”

The End

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s