Developer news from Aivosto (VBShop) - October 2004 1. Analyze Office VBA [new software] 2. Project Analyzer v7.1 [update] 3. SQLifter: Tool to understand VB6 database projects [new software] 4. Counting the number of statements [article] 5. Legacy code analysis [article] x----------------------------------------------------------------------x 1. Analyze Office VBA: Access, Excel, PowerPoint, Visio, Word Analyze and document Word VBA, Excel VBA, Access VBA, even PowerPoint and Visio projects. Examine call trees, view cross-references, list variables. Surf your VBA in hypertext mode. Document it as a web site. Understand how your code works. Enforce programming standards and detect dead VBA code. VBA Plug enables Office VBA analysis with Project Analyzer. Read more: http://www.aivosto.com/project/vba.html x----------------------------------------------------------------------x 2. Project Analyzer v7.1 Improve your VB or VB.NET code. Let Project Analyzer read your source and tell you what's in it. Feature highlights: * 149 metrics. Spot bad code. Project Metrics finds outliers - modules and procedures with exceptional metric values. Any rewrite required? * Add code review results to the VB.NET Task List. The improved Auto-fix repairs coding problems and inserts TODO comments in your source. * Project Printer turns your code to a web site with 12 new reports. See it for yourself. The demo works on your code, 10 files at a time. http://www.aivosto.com/project/project.html x----------------------------------------------------------------------x 3. SQLifter: Tool to understand VB6 database projects SQLifter finds the SQL in a Visual Basic 6.0 project. Understand how your VB6 system uses SQL databases. View the exact SQL used. View the SELECT, UPDATE, INSERT and DELETE locations. Determine where table X is being used in VB. Determine critical data access code, such as lines that update data. Read more and try the demo: http://www.aivosto.com/sqlifter.html x----------------------------------------------------------------------x 4. Counting the number of statements Did you ever need to count the lines in a program? You probably noticed that simple line counts have their problems. The more comments you add, the more blanks you put in, the more lines you split, the more lines you get - but no more functionality. Have you considered counting the statements? Statement counts are a more objective way to estimate the size of an application. You can count all the statements, declarative statements, executable statements or control statements. This article tells you more about counting the statement: http://www.aivosto.com/vbtips/stmt.html x----------------------------------------------------------------------x 5. Legacy code analysis Aargh! I just inherited a mess of projects from a team who left the company 3 years ago. I can't even touch that code without breaking anything. What do I do know? Read this article to learn techniques for understanding legacy apps. http://www.aivosto.com/vbtips/legacycode.html x-----------------------------------------------------------------------x You received this email because you have subscribed to the Aivosto newsletter. Unsubscribe/change: http://www.aivosto.com/mailinglist.html x-----------------------------------------------------------------------x Aivosto Oy, www.aivosto.com, vbshop aivosto.com We hope to hear from you! x-----------------------------------------------------------------------x