Actually storing the photos in a db file could be done without killing the backup medium if there was a daily FMServer near-line backup, which would overwrite every week, and an offline backup only once weekly, along with a program to weed the old offline backups.
You'd have to be very careful to not generate too many backups. There's a lot of unnecessary redundancy involved and the photos basically never change. IMHO, to do the above correctly is actually more trouble than the 'reference-only' method. -- Steve Gerow FileMaker 8/7 Certified Developer President Abrazos Data Consulting, Inc. Pasadena, California Member FileMaker Bus. Alliance > -------Original Message------- > From: Richard S. Russell <[EMAIL PROTECTED]> > Subject: Re: large photo file > Sent: Oct 01 '08 08:20 > > On 2008 Oct 1, at 2:21, Lee wrote: > > > 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 > > I use 2 files: File #1 contains essentially nothing but text > (photographer's name, image orientation [portrait, landscape, > square], date, nature of original [artwork vs. nature], copyright > status, chroma [color vs. sepia vs. B&W], etc.), and File #2 holds > the images themselves. The 1st contains links to the 2nd. > > This makes the whole shebang more portable and easier to back up. > Also, you can cart all of File #1 with you to a presentation and make > do with only a subsetted copy of File #2. > > If File #2 starts running up against any kind of limits, I can always > create a File #3 to hold additional images and jigger File #1 so it > knows which of the 2 image files to point to. Hasn't been necessary > so far, but I haven't been working on a project the size of yours. >
