Lee, Storing photos this size in a database can be a backup killer--the resulting file is huge and because it's modified every time a photo is added, the backup medium quickly fills up.
A better solution is to put the photos in a designated folder on a network drive and store the path to the photo in the db. This way the nightly backup only backs up the photos that were added during the day, rather than backing up the enormous photo db every time the mod date/time is changed. After saving photo to this designated folder, you can temporarily import it "as reference only" into a global container field. Create a calc text field with the formula "getastext ( container field )". This will display the complete info for the photo, including path. Save the complete path out to your db. Delete and repeat for next photo. -- Steve Gerow FileMaker 8/7 Certified Developer President Abrazos Data Consulting, Inc. Pasadena, California Member FileMaker Bus. Alliance > -------Original Message------- > From: Lee <[EMAIL PROTECTED]> > Subject: large photo file > Sent: Sep 30 '08 23:21 > > Hi, > I'm looking at a relatively simple Catalogue solution to handle > hundreds, maybe 1000's of photos where most of the file size for those > photos will be around 20MB. Does Filemaker still have a limit to the > size of a file ? > I will be using Filemaker Pro Server 9 to serve both PC and Mac machines. > The basics are quite simple, one file will hold the photos. The filename > for each photo will be the relationship link and a description will be > entered in the related file for each photo. > Very basic but the file size could be of concern > > Lee Mills >
