RE: Converting names & street names

Understood. However, using "software" to fix this will STILL not work
any better, because there will be names that will still get by that may
be JUST as high profile. It might only be, um, one, but it could be
"that" one... 

If you have the resources, I like the idea of following up with the
customer to confirm that the way you have their name is to their liking.
Otherwise, have a maintenance listing of all added names go to someone
who is responsible for getting it right... 

Dave

-----Original Message-----
From: midrange-l-bounces+dturnidge=oldrepublictitle.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+dturnidge=oldrepublictitle.com@xxxxxxxxxxxx]
On Behalf Of Alan Shore
Sent: Thursday, August 31, 2006 8:28 AM
To: Midrange Systems Technical Discussion
Subject: RE: Converting names & street names


No - don't get me wrong. I agree, the telephone operators entering data
should ALWAYS enter the data as best they can. The point I am trying to
make was that with the "human factor" and the amount of data input, zero
mistakes (although a nice goal to aim for) is NOT always attainable, and
when something does go wrong, Murphy's Law stipulates that its going to
be a high profile customer.

Alan

midrange-l-bounces@xxxxxxxxxxxx wrote on 08/31/2006 08:57:04 AM:

I don't think that makes sense. The "numerous telephone operators" are

going to have to put the name in anyway. Why not have them put it in 
"as best they can" and have it checked later. As I have been reading 
this thread, it would seem that changing the existing fields, and then

having them entered in Proper Case from then on would be the best way 
to handle it. Having a separate field would mean a file change (yuck) 
and recompiling, etc...

Dave