Don't store the photos in the database. Store them as files externally, and
only store the full path to each file in the database.

Access MVP Larry Linson has posted the following in the past:
The sample imaging databases at http://accdevel.tripod.com illustrate three
approaches to handling images in Access, and the download includes an
article discussing considerations in choosing an approach. Two of the
approaches do not use OLE Objects and, thus, avoid the database bloat, and
some other problems, associated with images in OLE Objects.

If you are printing the images in reports, to avoid memory leakage, you
should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
PrintFailure.zip is an Access97 MDB containing a report that fails during
the Access formatting process prior to being spooled to the Printer Driver.
This MDB also contains code showing how to convert the contents of the Image
control to a Bitmap file prior to printing. This helps alleviate the "Out of
Memory" error that can popup when printing image intensive reports.

A couple alternatives ...

(First, I'm with Douglas, don't store image files in Access... but!)

The newest Access ('07) supposedly does a better job of handling image files
(i.e., less "bloat").

Or, if you can connect to a SQL-Server database, you could store the images
in SQL-Server.  It will take a bit of coding to get them in and out...  I've
used this approach for a "Contracts" database, to help reduce the need for
storing paper documents.

The alternative is to put the image files in a known location
(folder/directory/path), with a known naming convention, then store the
location/path/filename in your database.

Regards

Jeff Boyce
Microsoft Office/Access MVP