I know I was relieved when duplication was disabled, since I have many lists and it was easy to forget I'd saved a cultivar before. I had to do a lot of deleting from forgetful, repeat "adding" of the same plant.So, that was a great improvement.
But, to try and understand the process more clearly ... I'm guessing you are letting us know that the program that saves a DB entry to our list/s cannot determine if we already have the plant saved and, if so, alert and offer an override option to allow it to show up more than once in the list/s?
The unintentional duplication function was truly hard for those, like me, who forget what is in various lists. And, overriding saved me a lot of clean-up. It's just that now it's _so_ nice and tidy that I'm actually using it as my primary source for tracking cultivars. It beats having to mess with excel or other DB programs, and printing it works to use the lists as a guide to work in the garden. For that reason, I began to wonder if I could somehow get an option back, by prompting from the DB when an entry already exists in my lists, but to have a second (or third, etc) duplicate allowed, with the ability to add different info in the notes section. In that way lots of natural and wanted duplications would be possible (different fans of same cultivar from different sources, unregistered tet conversions, even notes tracking individual seedling offspring until they are far enough along to have their own entry, and so on).
I could see how that kind of selective duplication might not be possible, though. That the DB is such a precise and versatile tool, surprising to me that it has already surpassed the usefulness of other programs, just leads easily to speculation about what else it might do!
