The main is required for something to run. Where it is depends on what you are doing. Since the SQLMethods is using the Connect class, the connect class itself doesn't want it. It doesn't sound like SQLMethods should be a runnable class either, but you can still test it with a simple:
And put that in the SqlMethods class.
public static void main(String argv)
catch (SQLException ex)
Think of your main as the entrance point to your program. If you create a jar file, one of the steps is to adjust the manifest file to determine which class will have the entrance point, and that class must have a main method.
Oh, I should mention as well. Almost every class I make in java has a main method. But its purpose is to test the class by itself with as little dependency on other classes as possible. Obviously with a SQLMethods you will need a dependency on the Connect class so that is certainly fine. I just won't use these classes as entrance point, I will use the class that uses these classes as the entrance point instead. So what I'm getting at is that the main method itself never needs to be removed, but only 1 main method will be called by your java program.