Developing Visual Basic Add-ins
by Steven Roman


Unconfirmed error reports are from readers. They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.


This page was updated May 10, 2000.


Here's a key to the markup:

        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification


UNCONFIRMED errors and comments from readers:


{45} The fifth line from bottom now reads:

	"Dim proj1, proj2 as VBProject"

This is a common mistake whereby the proj1 variable will be declared as a
variant type. The line should read something like:

	"Dim proj1 As VBProject, proj2 As VBProject"


{78} On the fifth line, the Clear procedure does not require any parameters.
The line currently reads:

	"Public Sub Clear(sText As String)"

Should read:

	"Public Sub Clear()"


{89}  The last sentence in the first paragraph in the section titled: "The 
Windows Collection" now reads: "...it has the same effect as setting the 
Visible property to True."

Should read:

	"...it has the same effect as setting the Visible property to False."


{97}  In Example 7-3, the third line of code reads: "Set winImm = gVBInst..." 
and the sixth line of code reads: "Set winActive = gVBInst..."

Should they read " = oVBE..."?



[97]  In Example 7-3, the last two lines of code read:

"winActive.SetFocus
 Set winImm = Nothing"

Why not also "Set winActive = Nothing"?