All I can think is that there's something fundamentally wrong with how I programmed my GUIs. I have a program that initially displays a GUI which has 6 buttons. Each of these buttons, when clicked, displays a GUI. One of these GUIs in particular is a JTable of "Teams". Each of these Teams has "Games played". You can click on the Team and click a button, "Display Games", to pop open another GUI that shows what games the team has played. When the user clicks "display games", anywhere from 1-7 copies of the SAME GUI are being displayed. In addition, when the user 'deletes' the games from the GUI (if he/she entered a game by accident) the number of times the program attempts to delete the game = the number of copies of the GUI that popped up. This happens despite the user only clicking "delete game" once. Everything in my program is scheduled on the Event Dispatch Thread. Java Sun says that the EDT for displaying GUIs and Worker Threads (for more time intensive tasks) are recommended.
I have spent over 75 hours building this GUI, all the background code/code that runs when the user makes entries is what I want it to be. I seem to be having problems with my GUIs though, I'm not sure exactly what the problems are. One of my users has complained that her Teams were completely lost, despite her not telling the GUI to 'delete' any of them. This seems like a memory consistency error to me, but I'm not sure. I've posted all of my code to the web at
Its a lot of code, but if anyone would care to run the program (the .jar is on the second page) then take a look that would be awesome.