VBACP System Version History

Change Details
Fixed an issue with some coding styles not working, plus added Office 2016 compatibility.
Fixed an issue with some coding styles not working – functionally the same but more robust profiling.
Same Version – Added a x64 version of the profiler library.
Fixed an issue with ‘Friend Sub’ and ‘Friend Function’ routines not cleaning correctly.
Fixed issue with pure 64 bit installations of Office.
Added improved error handling.
Fixed issue with pure 64 bit installations of Office. This would generate an error in previous versions of VBACP.
In the Access version, when forms or reports are intrumented, the previous version would leave the modified report/form open in design view. This fix resolves that issue and the design mode reports/forms are now closed.
Fixed an issue with the location of the .RST file.
Added interface into import module ‘basVBAProfiler’ to display the Debug Analysis form in Word and Excel versions. Added separate mde for Access version to run the debug wizard.
Fixed layout issue with tree based HTML reports.
Fixed an issue with profilling procedures/functions with a large number of parameters and these parameters are placed on many continuation lines. In some cases this would fail the instrumentation.
Removed the need to import the frmVBAProfiler and have included this into the libary itself. This was needed because Office 2007 and latter caused importing issues. Now, all you need to do is import the module basVBAProfiler.
Fixed issue with the location of the .RST file to now look for it inthe same location as your own file being profilled. Alos, removed the generic frmVBAProfiler and basVBAProfiler for environment specific version. So, from now on use the Excel, Word, or Access specific versions of these addins.
Fixed issue with projects named under Office 2007 style (like .xlsm). Fixed an issue with Help not working on x64 bit systems. Also, added interface ‘VBACP_ShowVersion’ to allow you to see what version of the software is loaded at any time by runnig this routine.
Added Access 2007 specific profiler library. Also, added interface module to allow the profiler to be used without the form based interface.
Corrected an issue with the profiler producing an error if the project had not been saved before running the profiler.
Corrected an issue with the timing accuracy (removed a significant portion of the profiler overheads from the measurements). These erroneous timings were introduced in the last major update (when the tree features were added). Fixed an issue with the Summary report not correctly reporting recursive routines. Significantly improved the performance of building the Standard Report for very large projects. Corrected an error that would appear occasionally when building a standard report for large projects.
Major Update: Added an additional report interface function ‘BandwoodProfiler.ReportDialog’ to display a dialog that will allow the user to create different reports (multiple formats on the same profile run).  Added a compilation const to each module that is profiled. This allows for the developer to build in special compilation code based on the presence or not of the instrumented code.  Added the ability to turn on/off the building of the calling tree. This is required for performance,  where very large projects may take between 10-50 times longer to execute with the calling tree enabled.  Added the ability to configure the CSV field separator (default is “,” comma) but can be set to anything you like via the CVSCharacter property.  Added a second CVS report type that has each value (ie name, count, and time) delimetered. This allows for each to be in a separate column for latter processing.  Added wildcard carapace to restrictions file format. So you may now can
have *=-1 or *=-2 as valid entries. Added a new report type. This report generates a calling summary (ie for each routine, what routines it called and the associated times. This routine is controlled via a new parameter to the Report interface.
Fixed an issue when the profiler would fail if a function has a commented ‘end function within it. Fixed a problem with recursive functions not profiled correctly and thus counted correctly. Enhanced the profiler to handle routines using the ParamArray declaration. Fixed an issue when a recursive routine is a function, the profiler incorrectly transforms the name so the recursions don’t go through the profiler counting.
Major Update: Added HTML and CVS formats styles to the standard profiler report. Also, added a hierarchical based report to profiler which is also available in text, CSV, and HTML formats.
Improved the ‘restriction.txt’ so that it now allows multiple files, one for each project being profiled. This is done via name of the restrictions file will now be the ‘project name.RST’.
Minor Update: Fixed an issue where a function name still hade the Profile_ entry left in after Cleaning the code. Added new functions to reporting. It now has two additional parameters, one to allow you to automatically overwrite the profile report file, or prompt each time. The other parameter, allows you to create a CSV file instead of the standard text output. Also, improved the data layout so its now sensitive to the size of your procedure names and the size of the values in the report.
Minor Update: Fixed an issue where a function name is followed by a comment on the same line and contains a closing “)” then the profiler would not transform correctly. Fixed an issue where a “Profile_” is wrongly added to some identifiers of user-defined types and constants. Fixed an issue where the ParamArray construct is not handled correctly. Fixed an issue where a “Profile_” is not added to the method name when it occurs as a parameter (and not removed at clean-up). Added new functions to allow you to block or completely ignore routines across profiling sessions. This is done via the restrictions.txt file.
Fixed an issue where the profiler would fail if the procedure that creates the profiled routines failed. Improved the error processing to provide better error reporting.
Fixed an issue where the profiler would not process all available routines and report that the program limit had been reached although it had not. Also, added a Debug Analysis Wizard to the main profiler form to facilitate analysis of user issues.
Fixed a number of issues to deal with tolerance of routine names. This will now accept more specific coding styles.
Minor Update: Fixed an issue where the profiled code would error when profiler limits were reached such as limit of modules exceeded, limit of functions exceeded. Fixed an issue with Access version failing of reports and forms had a hyphen within the reports/form name. Corrected an issue with the initialisation of the profiler form (new frmVBAProfiler form).
Under Office 2003, the profiler had a problem with early binding of the profiler object causing a compile error sometimes. This update corrects this issue.
Corrected an issue with the profiler not correctly profiling when module and class names contained spaces, such as “Gantt Builder”.
Corrected an issue with incorrect reference in the Excel version.
Major Update: Added Access 2000/XP and 2003 capability.
Corrected a problem introduced in the last update.
Added the capability for registered users to extend the limitations on the number of procedures/functions to be profiled.
Corrected a profiling issue with routine declarations with some non-standard variable declarations.
Corrected an issue with routines (subs/functions) not profiled correctly, if the entire routine was commented.
Corrected a number of issues with backward compatibility with Office 97 pre SR2 installations.
Major redesign to incorporate Office 97 through to Office XP. Also, made libraries Word & Excel specific to enhance profiling capabilities and remove the dependencies on ocx. Also, corrected an issue with underscore in some variable names.
Initial version.



  • Return to downloads

    Click HERE to go back to the downloads section.