HP3000-L Archives

March 2002, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael L Gueterman <[log in to unmask]>
Reply To:
Michael L Gueterman <[log in to unmask]>
Date:
Sat, 23 Mar 2002 09:15:47 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Hi Paul,

  I believe John Wolff mentioned something very similar, but using a
SOUNDEX routine on the last name should get a large percentage match.
Simply pre-process your employee's last name and write the
soundex(last-name)
value to a ksam file with some unique key (employee-id and full name?)
then you can do your normal matching run except add the check for the
soundex last name value against the pre-process file for verification.

Regards,
Michael L Gueterman
Easy Does It Technologies LLC
http://www.editcorp.com
voice: 888.858.EDIT or 573.368.5478
fax:   573.368.5479
--


Paul wrote:
>Fellow members,
>
>I'm looking for some ideas/suggestions on how to handle a task.
>
>I'm trying to develop a process that will delete from our server the user
>id of transferred/terminated employes.  On a regular basis I'll be getting
>from HR a list of employes and using a derivation of their payroll number
>I'll be deleting the corresponding user id.
<snip>
>The problem can be avoided if a further check of the employe's name is
>performed.  However there is no guarantee that the spelling of the name
>will be consistent, in the input file and our security database (Users
>could have been added by different application managers).
<snip>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2