Question on global fields

[laker_42]

If I define a global and place it on a layout and then I insert a graphic into the global field. Next I remove the global field off the layout. Does the global field still contain the graphic? If I set a field equal to the global field, would it give me the graphic that I inserted into it? I am asking this because I was looking at a sample file and in a script they set a field equal to a container field that contains a graphic. The only thing is is that I cannot find the global field any where on any layout. This led me to believe that I can set set a global field and then remove it and have it still contain the object. Am I way off in my thinking??? I have been working with FMP for a couple of years but now I am trying to see how other people do things in FMP. So I have been looking at sample files to get ideas on how to be a better developer. A lot of times I can figure out what the person is doing or how they are but this time I can't. Can anyone shed some light on this for me?

Thanks!

John

[laker_42]

I guess I should have done some testing on my own before posting this. I am able to accomplish what I was asking. I can insert an object into a global field and then delete it off the layout. I can then reference that global field by setting another field equal to it and it will give me the object that I inserted. That is kind of cool. My next question is would this be a recommended practice in certain situations or should it be avoided?

John

[jfmcel]

It is likely a good idea to use a developer's layout where you can easily access these global fields. But if you never want to see them again, excepts as they appear in your calc fields, delete away... you can always go to layout mode and get them back.

[CobaltSky]

What you're describing is a well used technique in some circles. It works well enough.

The only proviso to be aware of is that should a file set up in that way be saved as a clone at some point, the contents of the global fields will be lost, and must be restored or reimported in some way before the functionality will be regained.

This need not be a problem, but it's something to be mindful of, and to factor into your thinking about file updates or restore-from-backup procedures etc.