While it's possible to actually store the images within
the database itself as OLE objects, normally it's not the preferred way.
When you embed an OLE object in a table, you're storing a lot of overhead
as well. This overhead is the information about the object (such as it's
parent application) that Access needs to store in order to render the
object properly. For more details, visit this link
123151: Why OLE Objects Cause Databases to Grow
The preferred way to display images is to store the complete path
and filename to the actual files themselves within a table, and then use the Image tool
(in Access 95/97) to update the display. For details, check out this article.
148463: How to Display Image in Form Without Storing It in Table
Lastly, if you have a bunch of files in a folder that you need
to load into a table, then check out this article. Note: The
method described in the article actually loads the image in the table. If you don't
want to do that (see above), then you can simply save the filename in a string
158941: How to Load OLE Objects from a Folder into a Table
Also check out this article: Displaying photos in a form.