Hello -

I'm developing a multi-table solution (FM9 Adv for deployment on Mac/
Win network) in which each of 10 user tables has three layout views
(Form, List, Grid), all of which share the same button bar at the top
of the layout for commonly accessed functions like new, edit, delete,
navigation, etc.  In other words, altogether, there are about 30
layouts with the same button bar.

Now I can create the button bar once and assign all the tool tips and
scripts and then copy it to all the other layouts, but when I want to
make a change to one of the tool tips it means repeating that effort
30 times.  I can store the tool tips in a global field so that I only
need to change them there, but some of the tool tips are calculations
based on layout names, so that, for example, the tool tip for the new
record button will be something like "New " &
RightWords(Get(LayoutName), 1) so that a layout called Form Contact
will display the tool tip New Contact.  It's a little more complicated
than that as far as nomenclature goes, but you get the drift.

However, when I put a this calculation in a global field and reference
it from the button (e.g., Menu::gTips[2]), it shows up as literal text
rather than a calculation (i.e., it shows the formula rather than the
result).  I've tried a few variations to make it evaluate, but can't
seem to find the right solution.  Any recommendations?  Your help
greatly appreciated.

Thanks as always.

-J.

On May 1, 4:49 pm, jahn <jahnbigbo...@yahoo.com> wrote:
> Hello -
>
> I'm developing a multi-table solution (FM9 Adv for deployment on Mac/
> Win network) in which each of 10 user tables has three layout views
> (Form, List, Grid), all of which share the same button bar at the top
> of the layout for commonly accessed functions like new, edit, delete,
> navigation, etc.  In other words, altogether, there are about 30
> layouts with the same button bar.
>
> Now I can create the button bar once and assign all the tool tips and
> scripts and then copy it to all the other layouts, but when I want to
> make a change to one of the tool tips it means repeating that effort
> 30 times.  I can store the tool tips in a global field so that I only
> need to change them there, but some of the tool tips are calculations
> based on layout names, so that, for example, the tool tip for the new
> record button will be something like "New " &
> RightWords(Get(LayoutName), 1) so that a layout called Form Contact
> will display the tool tip New Contact.  It's a little more complicated
> than that as far as nomenclature goes, but you get the drift.
>
> However, when I put a this calculation in a global field and reference
> it from the button (e.g., Menu::gTips[2]), it shows up as literal text
> rather than a calculation (i.e., it shows the formula rather than the
> result).  I've tried a few variations to make it evaluate, but can't
> seem to find the right solution.  Any recommendations?  Your help
> greatly appreciated.
>
> Thanks as always.
>
> -J.

There's probably a way to accomplish what you want using the
Evaluate() function in the global.  But I think it would be easier to
use a custom function for Tooltips.  This article may require  a
subscription (I have one, but don't if it's required to view the
page): http://my.advisor.com/doc/17890.  Basically, you can use a
single custom function- Tooltip(tip) - with a very long Case()
statement as a central library for your Tooltips, instead of a global
table.

Yeah, I tried the evaluate function, but it was having it.  However,
the Custom Function idea seems promising.  The article is publicly
available, so I'll see where it takes me.  Thanks for the help.

-J.