If I can only think of 3 weaknesses in Excel that’s pretty good I think …. I love Excel, but I continue to be disappointed every day that being an expert in the product gets lower and lower in value. Frankly to do Excel right takes immense skill, lots of hard work, and not a little native capability (there seems to be a type of person who does this stuff well) and if companies don’t see that as a worthy professional pursuit then we are a dying breed I guess.
Given all that though, while trying to prove that Excel is a capable application platform (contrary to what some who visit here believe I’m afraid ….) my biggest beef of all is the fact that it is not possible to programmatically remove or change the password on a VBA Project.
In the absence of a compiler the only way I can protect my VBA source code from tampering is to place a password on the project. Tragically for the promotion of Excel solutions there is no way to affect this password programmatically in VBA (other than a kludgy Sendkeys solution that never seems to work). This makes maintenance nearly impossible.
I understand that a “REAL” Excel developer puts their Code in an Add-In and ships that as a separate file. But from my experience many users (and IT professionals) have trouble understanding the idea that two files are necessary. I want my code and spreadsheet all in one file … period.
I assume that one of you out there has developed a clever way to pull this off, but once again it is my belief that this should be basic functionality of the program and once again I consider this a weakness of Excel that I would like to see fixed.
Otherwise Excel is perfect in every way 🙂 ….