Are individual graphics or global fields faster?

[tv_kid]

I'm creating a 'standard' set of buttons to go on all layouts (navigation, return to menu etc). In the past I have simply added the graphic elements or images to each layout. However, on this particular project some users will be viewing the database (as a Filemaker client) over a VPN link, hence speed is a major factor. If I use global fields to store the graphics and use these fields as my buttons, will this increase the speed for the users? I guess what is mean is, does Filemaker 'cache' images in much the same way as a web browser?

Anyone else experimented with this and have any test results to share?

Thanks

[Søren Dyhr]

Neither, instead are elements build with the availiable toolspalet of boxes etc. stored as vectorized info and renders much faster than any jpeg or png! There are always a price to pay when vpn'ing speedwise, and some seek shelter under the separation model by having substantial "openers" on each users platform to avoid chattering in the networks - containing all graphichs locally.

But by and large are globals iffy if they interact with something stored on server via calc'fields.

Someone have told me that calc'fields as such, are to blame some of the slowness expirienced ...which have lead to a request to use CF's in every buttons script-parameter in a more modal kind of interaction, raising the number of indexes ...I can't say that I can substantiete this last point of view by expirience. But a lot of the network chatting is caused by globals interacting with calc's definition on server.

--sd

[Genx]

I doubt the graphics will play a large factor (unless they're huge or you're client is on a 56kbps connection). So as long as you shrink them to their nominated size before inserting them into FM, you should be problem free.

Alternatively, create a table full of unstored calc fields, referencing the images locally on the clients computer (this is how i get around speed issues).