> For example I would expect "Phe" would bring "Phelps, Bill" to the panel > without needing to hit the roll key even once. First screen on my system with that test ends at Sally Pheasant. One roll gets to Frank Phebas. (Okay, it's a pretty big database...) > My experience so far has been that as soon as you start making some > instances case-sensitive and other instances not case-sensitive for the > same field you create an uncertainty for the user. And, most users can > hit the shift key pretty easily. The solution we're using involves maintaining two fields for a person's name, one formated and cased as the person wants to see it, and a second field that is hidden from users that is maintained in all upper case, with the last word from the formatted field (before any commas) placed first in the field hidden field. The hidden field is used for all the sorting and searching. Peter H. Coffin firstname.lastname@example.org +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.