AnsweredAssumed Answered

Global container fields as icon placeholders

Question asked by user14360 on Feb 10, 2010
Latest reply on Feb 10, 2010 by user14360


Global container fields as icon placeholders


Hi.  I have started using global container fields as placeholders for some icons that I'm using throughout my database, instead of inserting the pictures directly into each layout.


I have a 'zImages' table, which has one record in it, and each field contains a particular icon I want to use. 


The benefits I can see of this are:

- if you ever want to change the icon, you only have to do it once (in the global container field)

- it would take up less space (not such a big deal, because the pics are tiny, but a benefit nonetheless)

- being globals, they can be placed on any layout in the database without relationships needed. 


This was working fine, it was remembering the icons I had inserted each time I opened the file, until I had another user connected.  (The database is hosted on Filemaker Server.) Then some of the icons started disappearing.  Now, I understand that globals are particular to an individual's session, and you have to set them on startup, but given that you don't seem to be able to set a container field on startup, how do I achieve what I'm after?


I'd prefer to have the icons actually within the database (not as a reference).


Do I need to make these fields NOT globals?  And have a 1 - 1 match field for the tables/layouts that I want to view them on?  (Seems unwieldy.)


Do I need two images tables? One without globals and the icons stored there and the other WITH globals and the fields being a calculation pointing to the record in the non-global image table?  This seems to be getting complex for something I was hoping would make my life simpler....


Or is there another alternative? 




Filemaker 10 Pro Advanced, Mac OSX