Known bugs and limitations in Project Analyzer 3.0.x

Please let me know of any bugs you find.

==================================
Known misbehaviour and limitations
==================================

- The size of variable, constant and procedure names is restricted to 64
  characters. Longer names are truncated.
- Long lines don't word wrap on most reports
- Reports to .wri files look ugly - use .txt or .rtf instead
- Some add-in functions (like ConnectAddIn) may show "dead"
- Constant references in the (declarations) section are not interpreted. 
  This may cause the following code to show WM_USER as a "dead" const:
  Global Const WM_USER = xyz
  Global Const WM_HELLO = WM_USER + 1
- ReDim MyTable(N) inside a procedure may be interpreted 
  as a new local array, even if it's a dynamic global array. 
  This is not a problem with module-level arrays.

- MyClass.MyProperty = 987      works OK (MyProperty Let), but
  MyClass(123).MyProperty = 987 doesn't (thinks it's MyProperty Get)
                                Problem with subscript.

- In the hypertext window, if you have two different definitions with the
  same name (e.g. Form1.MyVar and Form2.MyVar), the program may
  highlight the both in red when the other one is highlighted
- May produce OUT OF MEMORY or SUBSCRIPT OUT OF RANGE during analysis of
  extremely large projects.
  *** PLEASE LET ME KNOW IF YOU EXPERIENCE THESE ERRORS ***

=======================
Unsupported VB 4.0 code
=======================

- Compiler directives (#if xyz then)
- Line continuation character "_"

========================
Deficiencies in FRX view
========================

- Shows only graphical data.
  Textual data (like the List property of a ListBox) is not shown.
- Picture types may look strange, like (Icon) when it isn't an icon
- Doesn't understand if one control has more than 1 picture
  => Shows only one picture
- Understands the following properties: .Picture, .Icon and .MouseIcon
- Can't handle SSCommand.Picture. Seems to me these pictures
  are stored differently

================
For best results
================

- Always declare your local variables (use Option Explicit)
- Always save your files as text (VB 3.0)
- Use MS Word as RTF editor
- Wait for the analysis to end completely (it has 2 phases)