Haslett, Andrew
andrew.haslett at ilc.gov.au
Tue Oct 21 19:49:04 CDT 2003
I found/wrote a VBA equivalent a while ago.. Will see if I can find it. Cheers, Andrew -----Original Message----- From: David McAfee [mailto:DMcAfee at haascnc.com] Sent: Wednesday, 22 October 2003 10:07 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] "fuzzy logic" search Its an MS SQL function. Open QA, type in SOUNDEX, high light the word and press SHIFT+F1. Helps covers it a bit. D -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John Colby Sent: Tuesday, October 21, 2003 5:32 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] "fuzzy logic" search Hmmm soundex would be good though. Do you have this function? Is it a class, a single function? How does it work? John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Tuesday, October 21, 2003 8:20 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] "fuzzy logic" search John, I've received this kind of request before and I looked into it once. The fuzzy logic math was way, way beyond my grasp, so I settled for offering alternatives like soundex on the names. I created a customized soundex that used a number for leading vowels rather than the standard "vowel followed by number" pattern, so that if they misspelled a name with a leading vowel, there were still possible matches. But SSN? I mean, think of it. If a SSN has 9 digits, any one of which can repeat, how do you determine a mismatch by up to 2 characters? WHICH 2 characters? Charlotte Foust -----Original Message----- From: John Colby [mailto:jcolby at colbyconsulting.com] Sent: Tuesday, October 21, 2003 4:06 PM To: AccessD Subject: [AccessD] "fuzzy logic" search My client is having difficulties where the data input people are entering duplicate claims because wrong names or SSNs are entered. He's asked how difficult it would be to do a search for the names entered (seems irrelevant if it is wrong) but then has asked how difficult it would be to do a "fuzzy logic" search for SSNs that are different by up to 2 characters. I don't even have a clue how to attack something like that. Any ideas (other than "out the door, no parachute")? John W. Colby www.colbyconsulting.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not.