I dont understand why i get this error when trying to type "else"

Question

Hello Everybody,
Im new to java and am writing a simple program which gets a input number between 0 and 100 and is to print A for (grade>=90), B for (90>grade>=80) and so on, when grades < 60 get F.
i use a series of if/else, but when i get to the FINAL else it gets an error (red wavy line under the last else). this ruins the program bcoz now a grade 61 will output "D" AND "F".
can anyone explaing why this error msg? and how can i fix it?
this is the code:
public class Assignment02Q04 {
     public static void main (String[] args){
          int grade = (Integer.parseInt(args[0]));
          if (grade >= 90){
               System.out.println("A");}
                    else {if (grade >= 80){
                    System.out.println("B");}
                         else {if (grade >= 70){
                         System.out.println("C");}
                         else {if (grade >=60);{
                              System.out.println("D");}
                         else System.out.print("F");
     }

Answer 1

Please ignore the rude bits... this is a pro-forma post most often trotted out to suspected trolls... i.e. It's NOT directed at you personally.
h1. The Ubiquitous Newbie Tips
* DON'T SHOUT!!!
* Homework dumps will be flamed mercilessly.
* Have a quick scan through the [Forum FAQ's|http://wikis.sun.com/display/SunForums/Forums.sun.com+FAQ].
h5. Ask a good question
* Don't forget to actually ask a question. No, The subject line doesn't count.
* Ask once
    - Don't Crosspost!
    - Two people answering one question independantly is a waste of there time.
* Don't even talk to me until you've:
    (a) [googled it|http://www.google.com.au/] and
    (b) looked it up in [Sun's Java Tutorials|http://java.sun.com/docs/books/tutorial/] and
    (c) read the relevant section of the [API Docs|http://java.sun.com/javase/6/docs/api/index-files/index-1.html] and maybe even
    (d) referred to the JLS (for "advanced" questions).
* [Good questions|http://www.catb.org/~esr/faqs/smart-questions.html#intro] get better Answers. It's a fact. Trust me on this one.
    - Lots of regulars on these forums simply don't read badly written questions. It's just too frustrating.
      - FFS spare us the SMS and L33t speak! Pull your pants up, and get a hair cut!
    - Often you discover your own mistake whilst forming a "Good question".
    - Many of the regulars on these forums will bend over backwards to help with a "Good question",
      especially to a nuggetty problem, because they're interested in the answer.
* Improve your chances of getting laid tonight by writing an SSCCE
    - For you normal people, That's a: Short Self-Contained Compilable Example.
    - Short is sweet: No-one wants to wade through 5000 lines to find your syntax errors!
    - Often you discover your own mistake whilst writing an SSCCE.
    - Solving your own problem yields a sense of accomplishment ;-)
h5. Formatting Matters
* Post your code between a pair of &#123;code} tags
    - That is: &#123;code} ... your code goes here ... &#123;code}
    - This makes your code easier to read by preserving whitespace and highlighting java syntax.
    - Copy&paste your source code directly from your editor. The forum editor basically sucks.
    - The forums tabwidth is 8, as per [the java coding conventions|http://java.sun.com/docs/codeconv/].
      - Indents will go jagged if your tabwidth!=8 and you've mixed tabs and spaces.
      - Lines longer than 80 characters should be wrapped.
      - Proper indentation illustrates program logic.
* Post your error messages between a pair of &#123;code} tags:
    - That is: &#123;code} ... errors here ... &#123;code}
    - To make it easier for us to find, Mark the erroneous line(s) in your source-code. For example:
        System.out.println("Your momma!); // <<<< ERROR 1
    - Note that error messages are rendered basically useless if the code has been
      modified AT ALL since the error message was produced.
    - Here's [How to read a stacktrace|http://www.0xcafefeed.com/2004/06/of-thread-dumps-and-stack-traces/].
* The forum editor has a "Preview" pane. Use it.
    - If you're new around here you'll probably find the "Rich Text" view is easier to use.
    - WARNING: Swapping from "Plain Text" view to "Rich Text" scrambles the markup!
    - To see how a posted "special effect" is done, click reply then click the quote button.
If you (the newbie) have covered these bases *you deserve, and can therefore expect, GOOD answers!*
h1. The pledge!
We the New To Java regulars do hereby pledge to refrain from flaming anybody, no matter how gumbyish the question, if the OP has demonstrably tried to cover these bases. The rest are fair game.
Edited by: corlettk on 17/03/2009 23:25 ~~ Doh!