If you use the Step Over command, the Module window continues to display the current procedure while Visual Basic runs the GetQueryCriteria procedure. Execution then advances to the statement immediately after the call to GetQueryCriteria. Step Over is a better choice than Step Into if you want to stay within the current procedure and don't need to analyze the code in the GetQueryCriteria procedure. If you step into a procedure and then decide that you don't want to step all the way through it, you can step out of the procedure. When the Step Out command is carried out, Visual Basic runs the rest of the procedure, including any nested procedures that it calls, in one step.
Execution stops when it returns to the next line of code in the calling procedure.
You can freely alternate between the Step Into , Step Over , and Step Out commands. The command you choose depends on which portions of code you want to analyze at any given time. When you suspect a certain section of code contains an error, you may want to skip over it. This doesn't solve the problem, of course eventually, you'll have to debug that section. However, skipping lines of code enables you to move on and examine other parts of your code.