There is, however, one change you can't ignore in Win95. You could loop your code until a key was pressed. In fact, it made for a snappy response because the machine and the operating system weren't doing anything else anyway. But, if a VB module loops on itself and never frees the machine for other tasks, you lose system services such as the mouse and keyboard. Instead of looping to wait for an action, you need to assemble a collection of routines that execute whenever a specific event occurs.
Events are key pressed, mouse clicked, or timer expired.
The operating system informs VB of the event and places you at the start of the routine. You then run the routine and, when you exit from it, control returns to the operating system. This programming structure takes some getting used to, but my programs are improving with familiarity. The VB routines are contained in modules. A module can just be a collection of routines, or a form can be associated with the module.