Scott Golightly

At one time or another, most applications have to determine when a certain subroutine or function is executed and inform the user when an important event or an error occurred. Over the years, clever developers created different methods for these kinds of notifications. At some point in time, just about every Visual Basic programmer has tried using a message box to show when a method or subroutine was called. While this technique might work well for debugging, it's highly error-prone. Because there are legitimate times when a message box should be shown to the user, the developer can't just comment out every call to MessageBox. Instead, he or she would comment out each call to MessageBox as the messages appear during a debugging or testing session. Leaving a message box ... (more)

Multiple Active Result Sets and Asynchronous Connections in ADO.NET 2.0

In the early 1990s, I was working on a project in which we were creating an accounts receivable system. Because the users of the system would be dealing with people whose accounts were past due, the major concern of the client was that the windows open as quickly as possible. The ultimate goal was to have the main window in the application open in three seconds or less. We tried our best... (more)

Backup for Continuance of Operations

Every person who has ever been responsible for backing up data has had to ask themselves the same basic questions. They need to know what data has to be backed up, how frequently it changes, where to store the backups, and how quickly the data will have to be restored in case of disaster. The answers to these questions in a large way determine the media used to back up the data and the u... (more)