1 of 1 people found this helpful
This would get more traffic, if you move to Discussions, instead of here in Feedback (on the Community forum software).
Thank you for your post!
I am going to move this thread from the FileMaker Community Feedback Space, which is specifically for input on the Community itself, to the Discussions Space where you should receive more views and potentially more advice!
2 of 2 people found this helpful
You likely have your container field in the same table as your data. You can do one of two things...
Make the field a global container field, this way it is a single entry for all records. Also, it may be more useful to the field to a utility table instead of in your main data table. This one is personal preference but it helps keep things cleaner.
You could also put the logo directly on the layout - not in a field. My pref is to put it in a container field so that if the logo changes you only have to update a single field.
Remember that if you go the global container field route that the database file has to be local when you insert the logo file. Global fields are session specific. If the file is hosted on FileMaker Server the logo will not be there the next time you open the file.
3 of 3 people found this helpful
I would recommend putting the logo in a single-record settings table as a normal container field, then setting a corresponding global field equal to it when the database opens (as part of the OnFirstWindowOpen script). That way, you dodge the "I can only change the global field if the file's not hosted" issue. Just change the stored field, and it'll update itself automatically the next time any user opens the database.
That solves a problem I've been having - thanks!
thank you very much for all your answers, it helped me !!