Learn To Program With
(Last Update: September 7, 2008)
Every author endeavors for perfection. My apologies for the typos that have slipped
through. We'll do our best to have these corrected for the next printing.
None that we know of
- Page 76. 21KB should be 31KB.
- Page 91. Screen shot. Indicates "Report a
Visual Studio.Net issue" appears in the Start Window. This is a screen
shot from the Beta version--does not appear in the actual production Start
- Page 92. 3rd Paragraph. Indicates there is a
button called "Create Project". There is no such button. Select
"New Project" instead.
- Pages 92 and 93. c:\VBFiles won't show up in
the Location box until you make changes indicated on page 112.
- Page 93, last sentence indicates to select the
"Create Project" button--select the "New Project" button
- Page 94. Format menu will not appear until a
control is added to the Form.
- Page 103, Build Menu screenshot. After renaming
the project, this screen shot should indicate "Build ClasssDemo",
- Page 104, Debug Menu. By default, F11 is
Step Into. F8 was Step Into in the VB6 world. If you want to retain VB6
keyboard settings, select Tools-Options-Environment-Keyboard, and select
Visual Basic 6 as the Keyboard Matching Scheme.
- Page 110, Tools Menu. This is the Enterprise
view--depending upon the version of VB.Net you are running (or Visual
Studio) this screen shot may not match your view.
- Page 136, Step 6. You'll find that if you
change the Name property of the Form to frmChina, you won't need to make the
change indicated in Step 7--the Class name will automatically change.
- Page 137, Step 8. I indicate that after
changing the name of the Class, frmMain(China) will appear in the left-hand
drop-down ListBox. Actually, it will display frmMain.
- Page 145, Property list. The Name property of
the form is indicted as a 'documentation purposes only' property--as I
mentioned above, changing it also changes the name of the class.
- Page 150, Exercise 4-3. In order to prevent the
form from being maximized, set the FormBorderStyle
to FixedDialog NOT FixedSingle as the book indicates.
- Page 182, under the Name property. "Every
object in Visual Basic, with the exception of the form, has a Name
property." This is incorrect. The Form does have a Name property.
- Pages 184-185, Exercise 5-12. Instructions 3
through 8 refer to making changes to the checkboxes that appear inside of
GroupBox2. The references to GroupBox2 should be GroupBox1.
- Page 201, Exercise 5-21. Change the Enabled
Property of the Timer Control to True.
- Page 206, Excercise 5-22. In order to change
the TabIndex properties, you will need to fire 'unlock' the controls which
you may have locked, based on the Caution listed on Page 184.
- Page 241, Exercise 6-5. Title of the exercise
should be "Displaying Numbers from 1 to 10---The Loop Structure"
- Page 246. Debug.Print is no longer supported
(it was in the Beta version). Use ? intCounter in the Command Window instead
- Page 275, list of Data Types. You'll notice
that not all of the data types we discuss in the rest of the chapter are
- Page 279. At one time I say the Decimal Data
type consumes 8 bytes of RAM--in another, 12 bytes. 12 bytes is correct.
- Page 321, Exercise 8-4. There should be
parentheses around the argument list to the Console.WriteLine methods
(thanks Jonathan Spencer)
- Page 366, Exercise 9-8, Step 2. The line of
code beginning with strContinue = InputBox needs to be on a single line of
code---either that, or place a line continuation character after the word 'InputBox',
strContinue = InputBox _
I continue?", "The Indefinite Loop", "Yes")
- Page 399, the message box displayed is
incorrect based on the code entered on Page 398.
- Page 399, last sentence of paragraph 4. "intWheresTheSpace
is equal to 1." should be "intWheresTheSpace is equal to 5."
- Page 403, code. Notice that the Focus method is
executed, and it's missing parentheses--when you type these will be inserted
None that we know of
- Page 445, screenshots. List 'Assembly' as a
value for the Modifier property. You most likely won't see Assembly as a
- Page 509, discussion of the loop. "Let's
look at the body of the loop first. Amazingly, it consists of just this
single line of code." Amazingly, there are two lines of code
there---delete the second.
- Page 551. Screenshot isn't exactly what you
- Page 561. Screenshot isn't exactly what you
- Page 571, Exercise 15-2, step 2. The existing
code for the mnuColorsCustom_Click event procedure uses the variable
intRetValue not retValue as depicted here. It doesn't matter what you call
it--just be consistent.
The Number of visitors to this page since January
© 1998-2003, Smiley and Associates, Inc.
Revised - February 7, 2003
| My book!