I think you should only write static methods when you have a good explanation for their being static. I don't think you have supplied such an explanation.
Ray Bell wrote:. . . I like the idea of changing it to a static method . . .
Yes. Your code is full or repetitions as it stands. You can supply five Comparators<Book> and pass them all to the same method.
I looked at the possibility of using a comparator. The question is if this would really create more efficient, simpler code than the 5 methods I have right now in the class?
Why? What sort of algorithm are you using at present?
. . . Re: bubble sort. let's just leave that alone for now...
That's a pleasure
SchoolTextBookTry.java:207: error: cannot find symbol
if(book1.sortProperty.compareTo(book2.sortProperty) > 0)
symbol: variable sortProperty
location: variable book2 of type SchoolTextBookTry
creating an interface with 5 comparators, would take more code,
I have not yet used interfaces or comparators yet...
Did you find out anything useful in the Java Tutorials link I posted on Friday?
Ray Bell wrote:. . . coming across this new term Comparable, Comparator, etc.
Yes. The code Carey showed yesterday gives identical functionality to a Comparator<Book> only it is specialised to Books only whereas you can write a Comparator for any kind of object. It should be in the tutorials link I gave you.
. . . I should go back, create 5 comparators, use one method with two inputs, and choose a comparator based on the second input - property. . . .
You can have Comparators anywhere. Maybe the book class will have ready‑made Comparators, maybe AUTHOR_COMPARATOR or PAGE_COUNT_COMPARATOR. The String class has one rather like that. Or you can create Comparator instances wherever you are doing the sorting
can I just put the comparators into my Book class? . . .
When you pass the name of an array, it doesn't include 
I can leave out the  sign and everything will work just the same?
That's a pleasure
I appreciate all of your help.