I've inheritted a monster: the third party application has functioned wonderfully for over four years, but now the images that are stored in a general field have bloated the ftp storage area to over 1 gig. Jim, your right on target, the 'unmanageable' has happened in the form of corruptness simular consistant with messed up keys - a CDX rebuild, restore, is nessassary after each addition or change to the mentioned record field. Another project that I've worked on caught this problem during development, and I do reference the images directly: .jpg works great and actually uses less disk-space than if stored image in general field.
But back to the problem at hand, I have done everything that the product vendor has suggested: moved the project to a PC from the network.
This PC was top performance with no other possability of interference TSR's. We now have 'beta tested their product beyound' - can't use those general fields for image storage. That's why we want to dump all images back to (something like a jpg) so that we can continue to use the product (but not the general field), make our own reference (probably the key-value) to the jpg.

My boss figures that I can do to the third party product what I've done to my own project.
Naturally, I can't get my hands on any of the code for their product - so I do not know if there is any special format to their general field.
When I access their table I can pull up each image and morph it to make it readable and print it - but I can't afford to do that one at a time for each record.
Help.

>Not certain if I am on point with this thread. However, here are 2 cents anyway.
>We never store images in Fox tables. We store images as native files in a separate folder(s) and store a pointer in a(the) table. We also sometimes use image naming schemes, generated in Fox, to store information about the image in the image name.
>I don't know if VFP 6 tables are any different, but we found the bloat from image storage in FPW tables to render the tables unmanageable. We now manage multi-gigs of images for apparel applications, using VFP.
>
>
>>Sorry Edgar, I remember reading your original post. Please refresh my memory, what is the embedded file format?
>>
>>Neil

Edgar L. Bolton, B.S. B.B.A.