Containers are not displayed on FM go.
...when these are placed in a related table.
example : table of icons
How is your table of icons related? Is the Icons table in the same file, or on a server, or uploaded to the iOS device? Are the image field sizes the same on both devices' layouts? If not, are they set to shrink and/or enlarge to fit?
The table is in the same file. The size is correct.
Try turning off the Interactive setting on the container fields.
Any chance the images were stored by reference rather than embedded?
What format are the images? If they are not PNGs, I recommend converting them to PNG and re-embedding them.
Are format .png
conclusion final -> ... FMgo12 can not show pictures from other tables, ... less from other bd.
This has not been a problem for me... I have had no problem with related container based data in FMGO 11 or 12... Re-draw is obviously much slower in FMGO. But all data displays as it should. I mainly use PNG's with the alpha channels, Have also used jpeg's with no problem. It is strange that in the Monitor vs the iPad image you have there is a discrepancy. My first question would have been the same as Stephen's related to reference vs embedded.
1 db -> 2 tables 1 table with images (global fields), the other text data. You can see the pictures in the table (txt) ?
....with fmGo12 ?
Global fields???... If you have global fields I assume you are loading them from stored containers at startup. Globals do not store any data at all... In cases where a file is opened as single user session a global will generally hold the data that was set in the last single user session, this behaviour can be tricky to explain... I suspect that the Global fields may be your issue. A global also does not really require a relationship to display in an an unrelated table.
this is not valid for app. on fms.
I have to respectfully disagree... It applies to Global fields in general... Globals are not fields that store data (They sometimes seem that way in a single user session) but... They are session specific... Each terminal can have its own data in the same global field. In a multi-user environment... data would have to be entered somehow at startup... Either via a script or an auto enter.
FM Server will make the situation even more obvious... Usually in a single user environment when you re-open a file it will still have the data in the global field that was there when it was closed. When opening a FM Server hosted file... the globals will come up empty... In either case a Global field should always be thought of as a temporary/holder field. Never a field that would "Store" data.
Some people will load a set of globals from stored containers so they don't have to build relationships to the table... I prefer to have a table that holds one record which has any graphics that I want to access in Container fields... "NOT" globally stored. Then build an "X" table occurance/relationship to that table from all tables. That way you can get to the graphics from anywhere and you don't need all the extra fields created.
Hope this helps,
if load the fields with Fmpa and soon loads the file in fms, the images visualize all the users.
...sorry my english.
Retrieving data ...