thanks to all.
As Lynn suggested human intelligence was what I was hoping for; but
applied after the initial auto enter result from a custom function.
Agree with Grip, a proper calc is never going to be right all the time;
but if the cf could enter an initial suggestion, with the field then
allowing the user to correct the auto entry; that would be ideal.
Lyn, as for the apostrophe , van etc variations, the SmarterProper cf
seems quite flexible.
I was expecting that using the cf as an aec , and checking 'do not
replace existing value if any' would allow:
typing in the name,
the cf then forces its format
with a now existing entry, the user can correct the capitalisation,
without the cf re-triggering.
But FM !
If there is no existing value, when the first entry is made, when does
FM think it is going to apply the aec other than the first entry? I have
been converting calcs to aec as a general approach in a number of
solution revisions for the last 12 months, though probably always
unchecking the do not replace . So I am familiar with aec, but this just
doesn't compute in the cortex at the moment.