I think that there is a choice of philosophies here: 1. The function should be complex and accept any input and then attempt to convert it to an acceptable format.
2. The function should be simple, should publish its format requirements, and should expect the calling routine to send valid data. The problem with philosophy 1 is that the function will contain many more lines of code using more cpu cycles and may, in the end, make a wrong decision about manipulating the input. tjh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg Sent: Wednesday, January 05, 2005 2:17 PM To: [email protected] Subject: Re: [Hardhats-members] Unusual search failure. Be that as it may, I think it should be. I understand that users can be taught to only put in partial searches and select correct one from a list... but this is not sufficient for full database use. This became an issue during the uploading of transcription. The transcriptionist has to put the name of the patient on the report. In this case "DOE,JOHN D." The system looked for a patient by this name and couldn't find it because it wanted "DOE,JOHN D" Kevin ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
