There are some layouts in which the "powers that be" demand be in ALL
CAPITALS - not only for viewing pleasure, but also on exported text.

Setting the text to view all upper is easy.  However, if the user has
typed in lower case letters, that is what gets exported regardless of
what was displayed in the layout.

Aside from using an Upper function on every single field - any
suggestions on how to have the text actually changed to Upper case?
Thanks for any Tips, Tricks or Alcohol you can
provide!

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
WinXP Pro 64Bit / FMP Adv 8.0v2
VoicesInMyHead
a.k.a. The Voices
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

In the field definitions, you can change the auto-enter characteristics 
so the field uses an auto-enter calc and unmark the option so that it 
will replace any existing text.  That way, you can set the calc as 
upper(ThisField) and, whenever someone manually changes the value in 
that field, it will get replaced with all upper case when they exit the 
field.  For older records, you'll have to initially perform a Replace on 
those fields to convert their values to upper case.

Note that the auto-enter calc does not operate when you use certain 
script steps (like Set Field) to set them, so you'll have to make sure 
any scripts that write to those fields already write as upper().


VoicesInMyHead wrote:
> There are some layouts in which the "powers that be" demand be in ALL
> CAPITALS - not only for viewing pleasure, but also on exported text.
> 
> Setting the text to view all upper is easy.  However, if the user has
> typed in lower case letters, that is what gets exported regardless of
> what was displayed in the layout.
> 
> Aside from using an Upper function on every single field - any
> suggestions on how to have the text actually changed to Upper case?
> Thanks for any Tips, Tricks or Alcohol you can
> provide!

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg              (818) 883-2846
FM Professional Solutions, Inc.    Los Angeles

FileMaker 8 Certified Developer
Associate Member, FileMaker Solutions Alliance

On Tue, 14 Mar 2006 07:36:05 -0800, Howard Schlossberg wrote:
>  In the field definitions, you can change the auto-enter characteristics 
>  so the field uses an auto-enter calc and unmark the option so that it 
>  will replace any existing text.  That way, you can set the calc as 
>  upper(ThisField) and, whenever someone manually changes the value in 
>  that field, it will get replaced with all upper case when they exit the 
>  field.  For older records, you'll have to initially perform a Replace on 
>  those fields to convert their values to upper case.
> 
>  Note that the auto-enter calc does not operate when you use certain 
>  script steps (like Set Field) to set them, so you'll have to make sure 
>  any scripts that write to those fields already write as upper().



I'm annoyed that the functions know better than myself what I
want to do :-(

Take e.g. PatternCount - it's case insensitive within FMP7!?

What's patterncount("Take the A Train", "A")? It's 3...

If I would like to ignore the case, I'd use 

   Patterncount(Upper("Take the A Train", A)

However, there's no reverse function to make it case sensitive. I'd
have to check it separately via the 'exact' mechanisms - or maybe via
another field in Unicode indexing.


BTW: how does FMP8 handle the substitute functions? I wonder about the
syntax

  let([ cmd1, cmd2, cmd3], result)

compared to FMP7's

  substitute( text, [ a1, b1], [ a2, b2], [a3, b3])

instead of

  substitute( text, [a1, b1, a2, b2, a3, b3])

In fact I'd expect to live without the [] at all, since the if and case
functions show how to work without. You know where "[" and "]" are
hidden on the German Mac keyboard? I know, but it's always tedious.

- Martin