>Well, Michel, my request is extremely simple (though maybe not simple to implement). . . come up with some way to significantly reduce the chances of duplicate entries being made.
>

It's obviously not that simple, otherwise you would have posted a resolution. Most requests are "simple" to the person asking for them.

>I did NOT want to suggest any "solution" because I knew it would lead to something like this. BUT the fact remains that this is a serious problem and would be a very valuable thing to FIX.
>

That's kind of a cop-out. You need to give SPECIFIC ideas on what you think would be better. Imagine if one of your customers suggested that some part of an app you wrote needed to be fixed, but refused to give you concrete suggestions about what they wanted changed. How useful is that? Personally, I'd be really hestitant to change anything, w/o knowing more (and I spend a LOT of time thinking about useability in my apps).

Go ahead and step on some toes if you need to, to get your point across ;-)