Quote:
Can anyone verify my VISUAL BASIC application?
First of all, as programmer, it is your job to verify that your code is working as expected. If something is wrong, it is your duty to find and correct bugs.
Your code says that small sandwiches do not pay toppings.
Question: What if one want double cheese ?
-----
Your code do not behave the way you expect, and you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.
The downside of this solution:
- It is a DIY, you are the one tracking the problem and finding its roots, which lead to the solution.
The upside of this solution:
- It is also a great learning tool because it show you reality and you can see which expectation match reality.
You should find pretty quickly what is wrong.
Debugger - Wikipedia, the free encyclopedia[
^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[
^]
Basic Debugging with Visual Studio 2010 - YouTube[
^]
Visual Basic / Visual Studio Video Tutorial - Basic Debugging - YouTube[
^]
Visual Basic .NET programming for Beginners - Breakpoints and Debugging Tools[
^]
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.