Help  |   Contact Us  |   About Us  |   News and Events
Books, conferences, and other information about... Moving to Linux Switching to OOo Building Linux Apps Using Visual FoxPro
Buy      Download      Your Account      Catalog      Support      Conferences      Resources      Fun

Conferences - GLGDW 2006

The scoop on the 2006 Great Lakes Great Database Workshop.


Home
Late Breaking News
Schedule
Session Topics
  Battling Fox FUD
  Class Design
  Data Access
  Debugging
  Deployment
  Development Envir.
  Error Handling
  Middle Tier Compon.
  Performance
  Project Management
  Refactoring
  Reporting
  User Interfaces
  Vertical Mkt. Arch.
Related VFP Events
Speakers
Vendors
Registration
Hotel
Airlines
Maps/Directions
Where to Eat
Who's Going
Around Milwaukee
GLGDW 2006

Best Practices for Error Handling - Speaker: Rick Schummer

Error handling is an integral part of any application because all applications have natural and unnatural error conditions triggered as the users exercise the software. Visual Fox Pro has several techniques available to address these errors. Which is better to use? Should you implement an all encompassing, monolithic global error handler? Is the encapsulated Error method the route to go? Should you invest the time to modernize the architecture using the structured error handling introduced in VFP 8? Is a blend of the various options the best practice you should adopt? How are you going to be informed when the applications you support donít work as advertised?

This session will provide several best practice ideas to address the following issues:

1.Addressing the errors in your applications.

2.Errors can be different depending on the type of application (tradition desktop, client/server, Web).

3.Demonstrating all the error handling techniques available in Visual Fox Pro and discuss when you might use one over the other or integrate some together.

4.Determining the information you can trap so you know what went wrong, and where the user was when the trouble occurred.

5.Capturing the details and key information surrounding the error.

6.Communicating errors back to the development team so the problem can be fixed if necessary.

7.Tracking errors once they are reported.

Back to Top

Help  |   Contact Us  |   Legal  |   Privacy  |   Copyright  |   Join Our Mailing List