Mc MacH Mach chesnuts

Mc MacH Mach chesnuts

Post by Grip » Fri, 05 Dec 2008 12:23:34

On Dec 3, 5:16m, Chris Brown < XXXX@XXXXX.COM >

I wouldn't use Proper() calcs for last names. There's no way for a
calculation to know how an person prefers to spell their last name.
Train and trust your data entry person and make sure there's a way to
correct errors.


Mc MacH Mach chesnuts

Post by Lynn Alle » Fri, 05 Dec 2008 13:35:40

On 2008-12-03 19:23:34 -0800, Grip < XXXX@XXXXX.COM > said:

At some point human intelligence is the last resort. You could try
keeping a table of common "Mac" last names with appropriate
capitalization and flag the entries that dont' quite match, for human
intervention. But that's a big pain in the...

It becomes too unwieldy to keep the last name table, because you've got
O'Malley and Omar to worry about, Van De Voort and Vandevender, etc.

Best bet is to get a caring data entry person (hey some of us started
out that way) and/or to offer rewards for fewest mistakes.
Lynn Allen
Member Filemaker Business Alliance
Long Beach, CA


Mc MacH Mach chesnuts

Post by Grip » Sat, 06 Dec 2008 09:24:34

On Dec 4, 3:21m, Chris Brown < XXXX@XXXXX.COM >

FM has two options for auto-enter calcs...replace existing values or
not. That means the calc is evaluated at either record creation,
which is pretty helpful, or whenever any of the stored referenced
fields in the calc (including the field itself) are modified which is
also pretty helpful.

It sounds like what you're looking for is a way of having the calc
trigger when the field is modified the first time after record
creation. That can be done in a variety of ways.

One that comes to mind is to have a second field, Name Modified which
has the auto-enter Data checked and empty (for duplicating records)
and the auto enter calc box checked. That calc would be:
trigger = Name Field;

Then the calc in the Name Field would be:
Case(not Name Modified ; SmartProper(Name Modified); Name Modified)

Both auto calcs should be unchecked to always replace.

On record creation, Name Modified would be null. When a name is put
in the Name field for the first time, it would enter the SmartProper()
result. That entry triggers the Name Modified calc which becomes 1
and suppresses the SmartProper() from occurring again.

Mc MacH Mach chesnuts

Post by Chris Brow » Tue, 09 Dec 2008 10:30:23



yes, that's what I was after. Should have occured to me to use a control

My result
entry field: LastNameSP
control field: LNMmod

LastNameSP aec, allow replace existing:
LNmod = 1; NameLastSP;
SmarterProper ( NameLastSP ; 2 ; "" ; "Mc" & " & "Mac" )

LNMmod, aec, allow replace existing:
If( IsEmpty(NameLastSP) ; "" ; 1)