[AccessD] Re: "fuzzy logic" search

>The real way of "fixing" it would be to have a table of claimants and make
them select them from a list.

That's exactly what happens.  However in order to select the claimant, they
have to get the SSN right which isn't happening.

John W. Colby
www.colbyconsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Robert L.
Stewart
Sent: Wednesday, October 22, 2003 11:44 AM
To: accessd at databaseadvisors.com
Cc: jcolby at colbyconsulting.com
Subject: [AccessD] Re: "fuzzy logic" search


John,

If you break the SSN up into its 3-2-4 components,
it would make it a bit easier to do a compare.
I also assume that you would be using a mask
to prevent anything but numbers in it.

The real way of "fixing" it would be to have a table
of claimants and make them select them from a list.

I just did something similar with an ADP to get around
the number of records they would have in a combobox.

Give them 2 text boxes at the bottom of a "select" form
where they would enter the first 3 characters of the
last name and the first 3 of the SSN.  Then limit
the display to those that match and give them a "select"
button to grab the one they want to use.  I had the
select form pop up when I entered the field I wanted
to grab the data for.

Robert

At 07:36 PM 10/21/2003 -0500, you wrote:
>Date: Tue, 21 Oct 2003 20:05:43 -0400
>From: "John Colby" <jcolby at colbyconsulting.com>
>Subject: [AccessD] "fuzzy logic" search
>To: "AccessD" <AccessD at databaseadvisors.com>
>Message-ID: <DCEFJAOENMNENLAAOFGPGEHKFGAA.jcolby at colbyconsulting.com>
>Content-Type: text/plain;       charset="iso-8859-1"
>
>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