Optimize for what? For size, for speed, for usability, for extendability? Optimisation is the source of all evil (D. Knuth [from memory]). Mostly, optimisation is meant for speed, if not suggested otherwise. And mostly optimisation for speed will make the programm: - harder too read and maintain - bigger - harder to extend - harder to port Therefore optimisation for speed should be avoided if possible. Where speed-problems encountered? If yes, you should start with a profiler, finding the bottleneck, since often only a small amount of code is guilty for consuming much time, and only this is a candidate for optimisation. Another answer could be: rewrite it in asm Or implement it in hardware

GUI applications are for the most-part IO-bound anyways. So, it's not like you'd be able to optimize it at all. That is unless you have some giant calculation that it actually does at some point. Thus, the profiler comment by Stefan. The real question though is: is the program running too slow, or are you just wanting it to run faster because you can? Optimization is always in context of user needs. And therefore if the user is happy, then it is already optimized.

Hi, Well! the optimization that I sought was about speed. My program is not that slow. And database queries get you result in about 1 second (I am using SimpleText Database). The JOptionePane.showMessgae() that I am using to show property(realestate) details opens quite quickly. I see no such problems which might upset my user. The only minor problem could be the extra black dos-prompt screen that opens when it starts. Maki Jav