• ▼MSDN Library - April 2000
  • ▶Welcome to the MSDN Library
  • ▶Visual Studio 6.0 Documentation
  • ▶Office Developer Documentation
  • ▶Windows CE Documentation
  • ▶Platform SDK
  • ▶SDK Documentation
  • ▶DDK Documentation
  • ▶Windows Resource Kits
  • ▶Knowledge Base
  • ▶Technical Articles
  • ▶Backgrounders
  • ▶Specifications
  • ▼Books
    • About Books
    • ▼Advanced Microsoft Visual Basic 5
      • Foreword
      • ▶Preface
      • ▼Chapter 1: On Error GoTo Hell
        • ▼Introduction
          • Tip 1: Inconsistent as it is, try to mimic Visual Basic's own error handling scheme as much as possible.
          • Tip 2: Use line numbers in your source code.
          • Tip 3: Raise exceptions when possible because return values will be ignored.
          • Tip 4: Automatically log critical MsgBox errors.
          • Tip 5: Have an error handler in every routine.
          • Tip 6: Write meaningful error logs (to a central location if possible).
          • Tip 7: Use assertions.
          • Tip 8: Don't retrofit blind error handlers.
          • Tip 9: Trace the stack.
          • Tip 10: Use a ROOS (Resource Only OLE Server).
          • Tip 11: Replace useful intrinsic objects with your own.
          • Tip 12: Check DLL version errors.
          • Tip 13: Use Microsoft's MSINFO32.EXE when you can.
          • Tip 14: Treat error handling like transaction processing.
          • Tip 15: Don't test your own software or write your own test plans.
          • Tip 16: Stress test your applications.
          • Tip 17: Use automated testing tools.
          • Tip 18: Consider error values.
      • ▶Chapter 2: Patterns of Cooperation in Bytes and Blood
      • ▶Chapter 3: Empowering Your Users' Reports with Visual Basic 5
      • ▶Chapter 4: Transferring Information Over the Internet
      • ▶Chapter 5: Changing Your Approach to Visual Basic Coding
      • ▶Chapter 6: Migration Issues in Visual Basic 5
      • ▶Chapter 7: Staying in Control
      • ▶Chapter 8: Minutiae
      • ▶Chapter 9: How Does the Year 2000 Problem Affect Visual Basic?
      • ▶Chapter 10: Well, at Least It Compiled OK!
      • ▶Chapter 11: Multimedia and the User Interface in Business Applications
      • ▶Chapter 12: So You Want to Add Another User!
      • ▶Chapter 13: Database Access Options
      • ▶Chapter 14: Programming on Purpose
      • ▶Chapter 15: Didn't I Write That Function Last Week?
      • ▶Chapter 16: How to Juggle 30 Balls Blindfolded
      • ▶APPENDIX A Coding Conventions
      • APPENDIX B Changes in the DAO Structure
      • APPENDIX C Windows 3.11 API Calls
      • APPENDIX D Microsoft Product Date Limits and Formats
      • ▶APPENDIX E Is There Madness in Methods?
      • The Mandelbrot Set (International), Ltd.
    • ▶Developing International Software for Windows 95 and Windows NT
    • ▶Hardcore Visual Basic
    • ▶Hardware Design Guide Version 2.0 for Microsoft Windows NT Server
    • ▶Inside OLE
    • ▶Microsoft Jet Database Engine Programmer's Guide
    • PC 99 System Design Guide
    • ▶Programming the Windows 95 User Interface
    • ▶Understanding Thin-Client/Server Computing
    • ▶The Windows User Experience
  • ▶Partial Books
  • ▶Periodicals
  • ▶Samples