Sams Teach Yourself Visual Basic 6 in 24 Hours

By Greg Perry

• Table of Contents
  • Copyright
  • About the Author
  • Acknowledgments
  • Introduction
  • Who Should Read This Book
  • What This Book Will Do for You
  • Can This Book Really Teach Visual Basic in 24 Hours?
  • What You Need
  • Files on the Visual Basic Distribution CD-ROM
  • Conventions Used in This Book
  • Enough! Time Is Ticking!
  • Part I: Introducing Visual Basic
  • Hour 1. Visual Basic at Work
  • Hour 2.Analyzing Visual Basic Programs
  • Hour 3.Controls and Properties
  • Hour 4.Examining Labels, Buttons, and Text Boxes
  • Part II: Coding the Details
  • Hour 5.Putting Code into Visual Basic
    • Coding Basics
    • Data Basics
    • Expressions and Math Operators
    • Summary
    • Q&A
    • Workshop
  • Hour 6.Message and Input Boxes
  • Hour 7.Making Decisions
  • Hour 8.Visual Basic Looping
  • Part III:Putting Code to Work
  • Hour 9.Combining Code and Controls
  • Hour 10.List Boxes and Data Lists
  • Hour 11.Additional Controls
  • Hour 12.Dialog Box Basics
  • Part IV:Programming with Data
  • Hour 13.Modular Programming
  • Hour 14.Built-In Functions Save Time
  • Hour 15.Visual Basic Database Basics
  • Hour 16.Printing with Visual Basic
  • Part V:Sprucing Up Programs
  • Hour 17.Menus and Visual Basic
  • Hour 18.The Graphic Image Controls
  • Hour 19.Toolbars and More Graphics
  • Hour 20.Writing Correct Applications
  • Part VI:Advancing Visual Basic Applications
  • Hour 21.Visual Basic and ActiveX
  • Hour 22.Object Basics
  • Hour 23.Distributing Your Applications
  • Hour 24.Online Visual Basic
  • Part VII:Appendixes
  • Appendix A.Operator Precedence
  • Appendix B.Answers
  • Appendix C.Using the CD-ROM

Q&A

1. I don't like math, so will I not like VB programming?

   Visual Basic does all the math for you! That's why you learned the operators. People who don't like math use calculators, and people who don't like math can write VB programs.

2. If I want to represent a person's age value, which integer-based datatype do I use?

   The quick answer is that you should use the smallest datatype that will hold every value you'd want to assign. A person's age is rarely more than 100 and doesn't ever go past 255. Therefore, you could use a Byte datatype for a person's age. The Byte datatype is small and is much more efficient than a Long. You should now have the idea that you need to ensure that your variables can hold all the data required but that you should not use one that's too large and that will use unnecessary space. Having said that, the Byte datatype is really an exception to that rule! Byte is generally reserved for special system-level coding. Generally, the smallest integer programmers use is the Integer datatype, even though an Integer datatype is slightly less efficient than a Byte datatype because the computer has to transfer more information at one time when working with integers.

Share This