>If you must do this you can use keyboard commands to pull up the picture and issue an control v and then a paste special into a file. As mentioned by Arnon however, storing pictures, in general fields is a very disk wasting idea. Much better to store just the file name and use an ocx control, or what I do, use a web browser to display data, that way I don't
>have to worry about the fromat the multimedia is in (JPEG,AVI,MPEG, etc)
>
>HTH

I disagree with this opinion. Surely if we have few images we can keep them as separate files. But what's happened when we have thousand records? There is a bottom line: data stored in database! To avoid fpt bloating problem we have to create right data design:
1. Master file contains just links (foreign keys) to Image table.
2. Image table contain just 2 fields: ID and GenImage.
So deletion/creation records in Master file (frequent case) will not affect size of image table. Surely Image Table maintenance shoul include packing.