>The memo field is actually holding acrobat pdf files. I was getting to have just too many in the folder (about 200,000) so i put the name and description in a table row and then put the binary for the pdf in the memo. I was hoping not to have to have multiple tables as that will be about two tables a year. It is basically being used as a foxpro imaging system. Everything we print goes to the table and then I have a seperate program that reads that and prints them. So what will hapen when the fpt gets bigger than 2gigs? Mass corruption?
>
>thanx
>walt

What will happen? Let's just say that I wouldn't like to be in your shoes < G >. I don't know, really; but corruption seems probable.

Two tables in a year - that will require workarounds like SELECT ... UNION to fetch certain data. This really is troublesome.

I would also prefer everything in a single table, but don't know how to do this in VFP.

You could also keep the ideas of separate PDF files, have a folder, e.g., for each month, and keep the folder name as part of the stored filename, to simplify fetching.

Or, consider client-server - but this might be a major change in technology.

How about compression? Could you save a compressed version of your image?

If there is more than one image per record, you can also split your table vertically - each image field in a separate memo file.

HTH, Hilmar.