As Daniel has already pointed out, you'll need an intermediate
file. But, as Daniel also pointed out, you do not want to store
images in your database.
I have an application wherein the user has scanned or otherwise
obtained an image on the clipboard. I direct the file naming from
within the hosting form's class module where the user stores the
image. The application's tables contain the name of the file containing
the image and is correlated to the autonumber of the corresponding
record. E.g., c:\AppFolder\AppImages\Im000438.jpg.
My form has a command button, "Import Image", that creates an
empty jpg file and opens whatever graphics editor the user has
available. The user pastes his/her image into the current graphic
window and saves and closes the current graphic window. When
all other "required" information is completed, I save the pending
record into the database, obtain the autonumber assigned and
rename the image file accordingly, all the while poised to purge
everything if the user aborts the operation.
The application necessarily has "user installation parameters" that
are contained in one of its tables that, amongst other things,
specifies to the application user chosen folder names and what
graphics and/or text editors the application is to use.
Post back if you have any questions.
Bill