continues to execute in a completely predetermined path. The execution of code
might branch and loop on occasion, but the execution path is wholly determined by
the program. This often means that such a program is restricted in how it can
respond to the user. For example, the program might expect text to be entered into
controls on the screen in a predetermined order. This is unlike a Windows application,
in which a user can interact with different parts of the interface—often in any
order he or she chooses.
Visual Basic 2010 incorporates an event-driven programming model. Event-driven
applications aren’t bound by the constraints of procedural programs. Instead of the
top-down approach of procedural languages, event-driven programs have logical
sections of code placed within events. Events don’t occur in a predetermined order;
the user often has complete control over what code is executed in an event-driven
program by interactively triggering specific events, such as by clicking a button