The usual solution (aside from the attachment field in .accdb/e Access front-ends - where you don't really want to store that info if the front-end is deployed to the user PC) is to create a separate table of images that links to the related record using a foreign key. That lets you have an unlimited number of images. If you want to display those images, you can create an image control on the form and provide navigation buttons to scroll through the images. That does involve using VBA and DAO/ADO to scroll through the related record set. Another option is to use a subform that contains an image control.
Here are some references that may help you determine the best design in your situation:
Storing images in Access Databases
Storing Images and BLOB files in SQL Server
If you still have questions, please post back.
Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!