On Thu, 12 Oct 2000, Derek Lane-Smith wrote:
> I dunno, I think having two separate header fields would be cleaner and
> less confusing than having several options for the current K: field. If
> the two fields were both filled it provides some redundancy. If they were
> in conflict, you can generate an error message, that would be missed if
> there were only one.
Which is exactly a good reason for having only one field. Redundancy is
not good! Like in a batabase where you strive to register your information
exactly once.
--
Atte Andr� Jensen
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
