Quote:
|
1> I would go with the Alternative, i.e. it is either set or not.
|
Quote:
Originally Posted by theducks
Ditto , Seconded ..whatever  |
Here's why I disagree. Suppose I want to add a field to keep track of this data bit:
Mom has read this book. Y/N
Now think about a large collection. I know Mom hasn't read some books, and has read some others. How do I set this field for the other books? I could default to No, but then it's incorrect on everything she's read. I really want to not buy a copy for her of anything she's already read, but I need to find books she really hasn't read. I've got no way to keep track of which field is a true No, and which simply is due to my lack of information.
Tri-Valued is far more useful. If I want 2-valued, I just highlight all, bulk edit and set it to default N or Y.
Most of the time, these custom fields will get added to an existing database where the user won't have time to fill in every record correctly.