Although it isn't a typical calculation data type, you can do a few interesting things with container fields in calculations. You don't have the same vast options you do with other types. It would be great if you could subtract Cousin Clem.jpg from Family Reunion.jpg to get the
When you create a calculation field (Section 9.1.1), you can set its result type to Container. You can't create container data in a calculation, but you can refer to other container fields. When you do, the picture, sound, movie, or file in the referenced container field shows in the new calculation field.
You can, for example, make a calculation field that shows the contents of one container field when you're in Browse mode and another in Preview mode. This field lets you use
You might also want to use container fields in a calculated replace. Suppose you have a found set of 30 records that don't have a low-resolution image. You have to have something in that field, so you decide to take the hi-res image for those few records and plunk them down in the low-resolution image field. Choose Records Replace Field Contents and perform this calculated replace:
Graphics::High Resolution Image
The entire calculation consists of a reference to a field of that
If a container field holds a reference to a picture, movie, sound, or file, instead of the object itself (Section 2.7.4), you can do even more. When you treat such a field as text , FileMaker gives you some information about the referenced file.
If you have a field called Product Shot (see Figure 10-4) that holds a reference to a photograph file, you can use this calculation:
GetAsText ( Product Shot )
The result of this calculation looks like this:
size:266,309 image:../../../../../quilt database/sale quilt pix/batik squares.jpg imagemac:/babycakes/current work/quilt database/sale quilt pix/batik squares. jpg
As shown in Figure 10-4, FileMaker
You can use this calculation to help you keep track of a set of images that the whole company needs to use. You really need two container fields for this purpose. One holds the graphic itself, or a low-resolution copy, if you don't want the file size to balloon. Then, when you place the graphic as a reference in the second container field, the calculation stores the graphic's original location. The calculation's not dynamic, however, so the path serves as a reference of where the file
be, not where it really is. Company policy about