When coding it's easy to make small mistakes. Usually these errors have no direct effect, the code runs and everything seems to be o.k. That makes this situation so dangerous.
Over the years, you collect a lot of experience when coding. If you later review the code you wrote years ago, you surely will see potential for improvement. When you take over an application someone else has written, the situation becomes even more confusing. Here your success depends on how well your predecessor has complied with the rules and general knowledge.
If you want to gain a quick overview of potential errors you can use the TM VBA-Inspector. This Add-In let's you browse the entire VBA code of an application for potential errors.
Because there are different views about what constitutes an error and what not, you can toggle every single failure in the Options dialog to fine-tune the TM VBA-Inspector to your individual needs and your own coding style.
TM VBA-Inspector provides the following possibilities:
TM VBA-Inspector is an Add-In for the VBA Editor and can be used in Access 2000 and later versions.
Since version 1.45.50 the VBA code in Word, Excel and Powerpoint can also be investigated.
You can find more informations on the use of the TM VBA-Inspector in this article on the Access Team Blog.
|Start the download||for Access 2000 / 2002 / 2003 / 2007 / 2010 / 2013 / 2016|
Comment # 1: Anti-virus software
Unfortunately, it happens every once in a while that a manufacturer of anti-virus software classifies the TM-VBA inspector as a virus. I can say the following: I have developed the TM VBA-Inspector with great care. Also on my system an anti-virus software is used. Nevertheless - for understandable reasons - I can not express a guarantee to anybody.
My request at this point:
You can help me by telling me which anti-virus software currently classifies the TM VBA Inspector as a virus.
You can continue to support me by contacting the manufacturer of your anti-virus software and asking for an examination of the installation file of the TM VBA Inspector.
This procedure has already been successful several times.
In any case, I thank you at this point - also on behalf of future users - for your support.
Comment # 2: Installation unsuccessful
Unfortunately, in the recent past, I have received messages from users who can not install the TM VBA Inspector.
I have already dealt with the matter. Unfortunately I did not find a solution.
At this point I am looking for support:
If you are familiar with installation files and the log files created during the installation, I would be glad if you could give me a hint to solve the problem.
At this point you can certainly be sure of the thanks of the future users.