So how do you know when to stop debugging? Looking through this thread, the immediate problem is that there were 2 blank records in a table. Step up from that is that the user wanted to add 1 blank record, but ended up with 2. Well if the user needs to add blank records, you can't disable that functionality. But the step up from that is the user added the blank record so that she could have a blank option in a combobox. So now maybe the solution to the problem is to stop allowing blanks and add a blank option in the combobox. But to keep the debugging process alive, why was this not correct in the first place? Does this now bump up to the requirements gathering level to try to fix a bug in why this wasn't discovered to begin with, or can it now be successfully written off?

jfh