I totally agree with Jeff that trying to write the whole program at once is typically a bad idea. As you see, you often get a boat load of compiler errors that are difficult to track down. Jeff suggested one way of breaking the program into little steps. Feel free to break it down in a different manner, but the idea is to get a little part working before moving to the next part. This means that
you should write a FEW lines of code, compile it, run it, test it, then go back and write a FEW more lines of code. As a rule of thumb, you should probably write less than 10 lines of code at a time before attempting to compile your program.
Also, when I code, I find it best to type in sets of matching braces, parentheses, brackets, etc. FIRST and then go back and fill in the details. For example, I usually start by writing the class like this:
Notice that I'll type BOTH braces, then use the arrow keys to go back and fill in the main() method:
Notice that I again type in BOTH braces before going back to fill in the code inside of main(). I suggest that you get in the habit of ALWAYS doing this. It helps avoid errors due to mismatched braces.
You should also adopt some coding conventions AND STICK TO THEM RELIGIOUSLY. The exact conventions aren't the issue here; these will change over time and eventually will be dictated by a company's policy (if you are heading towards a coding job in your career, that is). However, consistent use of the coding convention is essential, in my opinion, to make your code readable, for yourself more than for others.
Probably the first two things you should decide in your coding convention is where to place the opening brace for a block of code. It looks like you are already consistently placing it on its own line. That's good.
Another coding convention deals with indentation. First you need to decide how large to make your indentation. I think Sun's suggested convention is 4-space indentation. Secondly, you need to figure out WHERE to indent. It's common practice to indent code inside a set of curly braces, but to leave the curly braces at the same level as any leading code (such as a method signature or an if statement). As an example, notice in my code above, the main method (which is inside the curly braces for the class) is indented one level and its curly braces are lined up with the method signature. If I were to insert code inside of main() it would be indented another level.
Adopting such conventions, and religiously sticking to them, will help you avoid many common errors, both at compile-time as well as run-time.
So my suggesting is just as Jeff says: start over and write a little bit of code at a time. As you do, follow some kind of conventions to help keep your code readable.
I apologize if this doesn't answer your questions directly. I hope that this helps you avoid bad programming practices now so you don't have to unlearn them later.
Keep Coding!
Layne