Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.
So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.
Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input Expected output Actual output
1 2 1
2 4 4
3 6 9
4 8 16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
int Double(int value)
{
return value * value;
}
Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!
[edit]
I have added
pre tags to preserve your formatting, but all that really did was make your code less likely for people to read, particularly when you see bits like this:
cout << "\n\nSave Data to Output File? (Y/N) ";
cin >> ans;
if (ans == 'y'|| ans == 'Y')
goto next;
else
goto next2;
next:
cout << "\nEnter Output Filename: ";
Sort your indentation out, get rid of every label and forget that
goto even
exists for several years, and you'll understand when it is appropriate to use and when it isn't. And I haven't used a goto in any code for nearly 2 decades ... so a relatively trivial task like this should not need any at all. Using them implies that you didn't sit down and think about your design before you sat down and rushed into code - and that's probably why it's so ugly, difficult to follow, and doesn't actually work! five minutes of planning can save you hours of pain and debugging, honest.
[/edit]
Submit an article or tip