Yes, as Bas said, you can use three fields or a separate table. Here's how
to decide:
If the picturesare of DIFFERNT things, i.e. a person, a map, and an
insignia, then you could store them in separate fields in the same record.
By the rules of normalization (yes, it is a 'z') they represent different
things and can therefore be in the same record.
However, if they represent the same thing, one or more pictures of a person,
map or insignia, then there should be a separate table holding them. (I
don't want to mislead you, it could also be pictures of different people,
maps or insignia as long as they fit the same category.) In this table,
there would be a Foreign Key field that holds the the value of the
corresponding Primary key in the main table and a single field to hold the
path. Each picture would have a separate RECORD in the other table, not a
separate FIELD.
Something like this:
tblMain tblPictures
------------ ----------
MainID (pk)--| PictureID (pk)
other fields.. |--<MainID (fk)
PicturePath