While it's possible to actually store the images within the Microsoft Access 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.
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 97/2000) to update the display.
The following example shows you how to display Windows bitmap images on a Microsoft Access form without storing the images in a Microsoft Access table.
c:\windows\circles.bmp c:\windows\waves.bmp c:\windows\tiles.bmp c:\windows\bubbles.bmp
Private Sub Form_Current() On Error Resume Next Me![ImageFrame].Picture = Me![ImagePath] End Sub
Private Sub ImagePath_AfterUpdate() On Error Resume Next Me![ImageFrame].Picture = Me![ImagePath] End Sub
Note: You may need to amend the file paths and image names to correspond with images stored on your system.
The method described above is similar to the actions required to include a bound image in a report. There is a further article related to this at: How to include a bound picture in a Report