I'm working on a database for a client involving two files: a contact file and thumbnail viewing file. The thumbnail viewing file has two layouts: the main layout with 10 container fields for viewing of the low-res thumbs, and a Print layout with 4 containers in a 2x2 format. The files are related through jobs that are being performed with the client's customers.

Through use of the Troi file plug-in, I'm able to get 10 low-res thumbnails per record into the thumbnail database. The user selects which thumbnails they wish to collect for output and selects "Print". This launches a print script, and the Troi file plug-in again does its job, this time referencing the thumbnails selected for output and importing the large original images in a 2x2 output page.

Each of these images can be anywhere from 200k-600k in size. The images which are imported are then deleted from the printable layout at the finish of the print script.

The database performs well. It's not as snappy as it can be, but not bad. The issue is that, when running through the Troi-assisted print script, the thumbnail database grows to an unmanageable size (e.g. 18MB from 1MB after printing one 2x2 output page). On occasion, quitting the database will decrease the size to the original size, although not always. Obviously, this is unacceptable for long-term use.

I'm trying to determine this: is this just an issue with filemaker when dealing with / printing large image files, or is it more likely an issue with something internally?

Any help would be greatly appreciated!

Hewpie

Sorry, but why is 18MB an unmanagable size? Filemaker will happly work up to 2GB in size.

Since you are basically clearing the file after every printing, I might suggest you do not use the original file for this work anyway. Make clone of the picture file on the users local machine. Then do the work in that file, deleting it afterwards.