Errata
The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted By | Date submitted | Date corrected |
---|---|---|---|---|---|
Printed | Page xxv |
Support URL has changed |
Microsoft Press | Jul 13, 2010 | |
Printed | Page Last Page |
Correction To Software Requirements |
Microsoft Press | Jul 13, 2010 | |
Printed | Page xvii |
Support URL has changed Page xvii: Support URL for Microsoft Press has changed. Change: http://mspress.microsoft.com/support/support.htm To: http://www.microsoft.com/learning/en/us/training/format-books-support.aspx |
Microsoft Press | May 06, 2010 | |
Printed | Page 35 |
Error In Step 2 There is an error in step 2 on page 35. Change: "Type End, and press the Down arrow key." To: "Type End and press the Down arrow key." |
Microsoft Press | May 06, 2010 | |
Printed | Page 91 |
"menu list" should be "dialog box" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 118 |
Program Statements Are Covered in Lesson 2 On page 118, in the first paragraph it states that you learned about program statements in Lesson 1. Actually, program statements were not introduced until Lesson 2. Change: "As you learned in Lesson 1, a line of code in a Visual Basic program is called a program statement." To: "As you learned in Lesson 2, a line of code in a Visual Basic program is called a program statement." |
Microsoft Press | May 06, 2010 | |
Printed | Page 135 |
Incorrect Formula |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 197 |
Error In Code Sample Page 197 contains a code error in the "Lesson 7 Quick Reference" section Change: "If InpName = "Trotsky" Then ExitFor" To: "If InpName = "Trotsky" Then Exit For" |
Microsoft Press | May 06, 2010 | |
Printed | Page 225 |
Use Resume with Label Rather Than Resume Next with Label |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 252 |
Incorrect Forward Reference On page 252, the parenthetical statement that concludes the second paragraph has an incorrect forward reference. Change: "(The Move method also lets you adjust the height and width of an object. See the One Step Further section later in this lesson for an example.)" To: "(The Move method also lets you adjust the height and width of an object. See Expanding and Shrinking Objects While a Program is Running later in this lesson for an example.)" |
Microsoft Press | May 06, 2010 | |
Printed | Page 307 |
Explanation Of Dimensions Technically Incorrect |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 335 |
Error In Sample Code Table The table on page 335 contains an incorrect code sample. Change: start% = InStr("bob", "bobby") To: start% = InStr("bobby", "bob") |
Microsoft Press | May 06, 2010 | |
Printed | Page 361 |
Delete Underline Character |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 392 |
Code Modification For Excel 2000 Compatibility On page 392, the 7th line of sample code will need to be modified to be compatible with Microsoft Excel 2000. All the Microsoft Office Automation examples were written originally for Microsoft Office 97, which was the current version when Microsoft Visual Basic 6.0 was released. Change: Set xl = CreateObject("Excel.Sheet") To: Set xl = CreateObject("Excel.Application") |
Microsoft Press | May 06, 2010 | |
Printed | Page 467 |
Problems Loading Project in Lesson 18 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 536-551 |
MyDHTML7 May Display An Error When Executed Page 536-551, Lesson 22: If you attempt to run the MyDHTML7 application, you may experience an error such as "Type Mismatch". To avoid any errors, perform the following steps:Start Lesson 22 using the project you created in Lesson 21.On Page 545 change: Result.innerText = "Wins: " & GetProperty(BaseWindow.Document, "Wins") To: Result.innerText = "Wins: " & GetProperty(Document, "Wins") On page 546 change: x = GetProperty(BaseWindow.Document, "Wins") Result.innerText = "Wins: " & x + 1 PutProperty BaseWindow.Document, "Wins", x + 1 End If End Function To: x = GetProperty(Document, "Wins") Result.innerText = "Wins: " & x + 1 PutProperty Document, "Wins", x + 1 End If End Function On page 547 change: PutProperty BaseWindow.Document, "Wins", x + 1 To: PutProperty Document, "Wins", x + 1 MORE INFORMATION Lesson 22 was written with an early version of Visual Basic 6.0. The released version of Visual Basic 6.0 generates slightly different code for DHTML applications than the pre-release version. For example, the pre-release and released versions of PutProperty and GetProperty have different parameters. Pre-release version: Sub PutProperty(strName As String, vntValue As Variant) Function GetProperty(strName As String) As Variant Released version: Sub PutProperty(objDocument As HTMLDocument, strName As String, vntValue As Variant, Optional Expires As Date) Function GetProperty(objDocument As HTMLDocument, strName As String) As Variant Depending on the book printing, the code in the book that calls PutProperty and GetProperty is different. Printing 1-2: Result.innerText = "Wins: " & GetProperty("Wins") x = GetProperty("Wins") PutProperty "Wins", x + 1 Printing 3-9: Result.innerText = "Wins: " & GetProperty(BaseWindow.Document, "Wins") x = GetProperty(BaseWindow.Document, "Wins") PutProperty BaseWindow.Document, "Wins", x + 1 Printing 10+: Result.innerText = "Wins: " & GetProperty(Document, "Wins") x = GetProperty(Document, "Wins") PutProperty Document, "Wins", x + 1 Depending on the book printing, the code on the CD will be different. Printing 1-9: Sub PutProperty(strName As String, vntValue As Variant) Function GetProperty(strName As String) As Variant Result.innerText = "Wins: " & GetProperty("Wins") x = GetProperty("Wins") PutProperty "Wins", x + 1 Printing 10+: Sub PutProperty(objDocument As HTMLDocument, strName As String, vntValue As Variant, Optional Expires As Date) Function GetProperty(objDocument As HTMLDocument, strName As String) As Variant Result.innerText = "Wins: " & GetProperty(Document, "Wins") x = GetProperty(Document, "Wins") PutProperty Document, "Wins", x + 1 Due to a change in the browser object model, the code "Basewindow.Document" generates an error in Internet Explorer 5.0. Using just "Document" should work correctly in Internet Explorer 4.0, Internet Explorer 5.0, and Internet Explorer 5.5. Whether Lesson 22 will run correctly without modification depends on the following conditions:The book printing.Whether Lesson 22 was started using the reader's Lesson 21 project or the Lesson 21 project on the CD.The version of Internet Explorer being used. |
Microsoft Press | May 06, 2010 | |
Printed | Page 537 |
Steps For Deleting An Element May Not Work |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 539 |
Coin Image May Display Blue Border Once you have completed Step 3, on page 539, you may notice that the coin image displays with a blue border. To correct this, you will need to set the Border property for the Image element to 0. The following steps will correct the problem. Make sure the Image element is selected. In the Properties window, scroll to the Border property, and click the text box to the right of the property.Type 0 in the Border property and press Enter to ensure the Image element does not display a border.Click the Save Project button on the Visual Basic toolbar to save your changes. |
Microsoft Press | May 06, 2010 | |
Printed | Page 548 |
Warning May Appear When Using Internet Explorer 5.0 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 552-553 |
Correction To Lesson 22 Quick Reference On page 552, at the bottom of the page, change: PutProperty "Wins", x + 1 To: PutProperty Document, "Wins", x + 1 On page 553, at the top of the page, change: x = GetProperty("Wins") To: x = GetProperty(Document, "Wins") |
Microsoft Press | May 06, 2010 | |
Printed | Page 572 |
Correct Path |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 594-597 |
Revised Instructions For Creating Custom Data Environment The steps outlined on pages 594-597, in the "Create a custom data environment" section of lesson 24 were created with an early version of Visual Basic 6.0. Additional steps may be necessary and are not included in the instructions. Revised Instructions:On the Visual Basic Project menu, click the Add Data Environment command. In the Data Environment window, right-click Connection1, and then select Properties from the shortcut menu. The Provider tab of the Data Link Properties dialog box appears, which allows you to select the provider you want to use to access your data.On the Provider tab make sure Microsoft OLE DB Provider For ODBC Drivers is selected and then click Next. The Connection tab is displayed, which prompts you for the source of your data.Click the Use Data Source Name option button, if it is not already selected, click Student Records in the drop-down list box, and click OK.Click the Add Command button on the Data Environment toolbar. The Add Command button creates a new ActiveX data object in the Data Environment.To set the unique attributes of this data object, right-click Command1 in the Data Environment window and select Properties from the shortcut menu. In the Command1 Properties dialog box, type InstuctorTable in the Command Name text box. InstructorTable will be the name of your recordset object when you use this ADO command later.Click the drop-down list box to the right of the Database Object option button, and click the Table type.Click the Object Name drop-down list box, and click the Instructors table.Click OK to create the InstructorTable command in the Data Environment.Click the plus sign next to the InstructorTable command to expand the table and see its fields.Open the Project window, and click the DataEnvironement1 designer.On the File menu, click the Save DataEnvironment1 As command.Type Instruct, and press Enter. If you are told that this file already exists on your system, choose a new name to protect the original version. |
Microsoft Press | May 06, 2010 |