>I've no argument with you and Tore that separate image files may be better if you're frequently editing them (contributing to bloat), or pushing VFP's 2GB table limit. Fortunately neither condition applies in my apps, and I'd simply rather deal with one table rather than thousands of individual image files for file management purposes and data backup. I call UDFs from my forms and my reports' detail bands that extracts and uses an active-x to convert the stored .jpg image to a temporary .bmp for display and printing. I find VFP plenty quick enough to handle it, though I'm also fortunate in that no form or report shows more than one image. So my particular set of circumstances lets me be bit of a relational database purist and keep all the images in a table column. I certainly realize that other techniques may be better under different conditions - just one more demonstration of VFP's remarkable flexibility.

Personally, I have kept separate image files, but in theory, I like the idea of using memo fields. I say in theory, because I didn't try this approach myself.

I think it would depend on some factors, including expected size (will approach the 2 GB limit, or not), which approach is better for a specific purpose.