Thank you everyone:

I guess this is what summer homes are for. *Re-writes*. I am going back to my app and and my summer home to re-write the images module so that PHOTOS.DBF holds a reference to the images stored in a seperate images folder rather than the actual image files.

Regards to all
Neil

>Hi,
>Due to the poor design of the referencing in FPT's, storing this amount of data will cause problems at some stage. Store the images in a separate folder & have a link to it, it is slower, but doesn,t break.
>
>>Fpt file fragility
>>
>>
>>I have a vfp application in service since 2001. The application keeps a database of clinical photographs. JPEG image files that are 300KB in size are stored in the memo field of my data table named PHOTO.DBF.
>>
>>PHOTO has three fields:
>>ID (c6) unique record identifier
>>PTNO (c6) unique patient identifier
>>Photo (M) holds 300 KB jpeg image
>>
>>After 3 years windows explorer reports that PHOTO.FPT has grown to a 995 Meg size file. Is there an upper limit to the size of an FPT file? I am well below the record limit for the parent table PHOTO.DBF but the size of the fpt is starting to concern me. Also… last night the FPT became corrupted. Any file can become corrupted but I am wondering if I am sitting on a time bomb.
>>
>>Any thoughts?
>>Neil