I'm building a solution that uses a somewhat fancy (for me) set of calculated container fields as a button-placing / altering system for basic navigation.

I.e., at the top of each layout I have an identical set of calculated container fields that conditionally display button icons according to what layout is being viewed and by whom. The actual button definitions are of course attached "over" the container fields. Everything works like a charm, EXCEPT --

When I want a user to be able to go into Find mode, all of the calculated container fields (i.e. the entire set of navigation buttons) disappears, because FMP thinks the container fields are subject to being searched. This occurs even though I have unchecked "In Find Mode" under "Allow Field to be Entered" (in "Field Behavior..") for each calculated container field.

This is a big problem for me as I have over 25 separate data layouts and don't want to even think about making 25 custom layouts just for Finds, with static buttons that I have to hand-program for every layout. I also don't want to get into the complexities of doing all Finding via scripts & Peform Find steps.. Seems redundant and a waste of energy compared to just using FMP's "Find" mode.

Any suggestions?

Thanks so much.

Turning the recieveing field global helps, but the means to fill it is restrained to oldfasion lookups - but investigate the upload!

--sd

GlContainers.zip

Why not make the calculation field itself global?

Obviously a much better suggestion, the speed of oldfasion lookups lacks something to be desired!

--sd

Thank you very much. Works like a charm. (Duh, why didn't I think of that?)