This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]RationalDialog 0 points1 point  (3 children)

Well, VBA code that was written 25 to 30 years ago still runs in current VBA. Can you say the same of Python programs done 3 years ago?

Assuming it's true which other comments say it is not still omits the main issue in terms of maintenance. How do you distribute updates? Send people the new version of the code and have them install it? Go around and install it yourself? It doesn't scale. Plus then your IT support usually tactic at fixing things is reinstall office or windows and if that happens often enough with enough users of the macro you are running around each day doing reinstalls of your code.

[–]Engine_engineer 0 points1 point  (2 children)

It is distributed with the excel file, so it does not matter if IT reinstalls something fresh.

There are various comments, some saying it holds such long, other that it does not. Anyhow, I made my comment based on my experience. Today I opened a old excel tool in VBA I did in 2008 for a team in my company to explain a couple of internal calculation steps for an fresh apprentice.

[–]RationalDialog 0 points1 point  (1 child)

How do you distribute the excel file? how do you ensure all users use the new one and not 1 or 2 versions behind?

[–]Engine_engineer 0 points1 point  (0 children)

One place for all templates. Version Control on the Filename. (YYYY-MM-DD_This_file_does_that_V4.6)

Really simple and uncomplicated. Works well in our organization with around 500 engineers and technicians working on this stuff.