This inquiry may seem like a redundant, yet my Google group search did
not return many relevant answers. My database experience lies outside
FileMaker, yet now I am making the transition to FileMaker and need
some assistance.

I would like to create a database that list jpg files with a viewer,
which display one image. One could select the jpg file in one text box
and the viewer updates with the image. The images would be tied to a
main record.  Now, it sounds like the standard photo catalogue
template, yet may be more involved. My scenario involves attaching a
random number of photos to one record; The record would have one an
index field and the images would be named by the index field with some
trailing numbers; e.g. RF05-25-04-001.jpg; the database record would
contain a field that list all filenames that correspond with the index
name and a viewer container; the viewer container would preview one
photo at a time depending on the selection in the field. 

Imagine a real estate database (not my scenario, but an easier example
than mine). The database tracks any number of houses; each record
represents a house with relevant data; each house has numerous photos;
one house may have 5 photos or 50 photos depending on the size of the
property and scope of detail. I rather avoid listing fifty container
fields for these photos; but rather list a file list from a folder
with viewer interface.

This objective may require multiple databases and scripting. Again,
these concepts do not intimidate me since I have extensive experience
with databases like Access & VB. I just need some helpful advice and
leads to information to get me up to speed. 

Hopefully, someone could give me additional insight on a solution.

I will use FMP 7 terminology of tables, but understand this mean files in
earlier versions of FMP.

I suggest one table (file) for houses, another for photos.

In both tables, have a house number field, that relates each house to all
its photos. In the house numebr table, this should be an automatically
generated serial number than can not be changed.

In the Photos table, besides the house number field, have a container
field for the photo, one photo per record. That way you can have any
number of photos related to any house. You can also have other fields for
description, date, etc.

When you get your photos, either direct from a digital camera or from
scans, you can import each folder of photos directly into the FileMaker
photo table (file). Assign the correct house ID to the photos for each
house when you do the import.

You can have a portal in the House file showing the related photos, and
just scroll through them.

Bill

Robert Neville wrote:

> This inquiry may seem like a redundant, yet my Google group search did
> not return many relevant answers. My database experience lies outside
> FileMaker, yet now I am making the transition to FileMaker and need
> some assistance.
>
> I would like to create a database that list jpg files with a viewer,
> which display one image. One could select the jpg file in one text box
> and the viewer updates with the image. The images would be tied to a
> main record.  Now, it sounds like the standard photo catalogue
> template, yet may be more involved. My scenario involves attaching a
> random number of photos to one record; The record would have one an
> index field and the images would be named by the index field with some
> trailing numbers; e.g. RF05-25-04-001.jpg; the database record would
> contain a field that list all filenames that correspond with the index
> name and a viewer container; the viewer container would preview one
> photo at a time depending on the selection in the field.
>
> Imagine a real estate database (not my scenario, but an easier example
> than mine). The database tracks any number of houses; each record
> represents a house with relevant data; each house has numerous photos;
> one house may have 5 photos or 50 photos depending on the size of the
> property and scope of detail. I rather avoid listing fifty container
> fields for these photos; but rather list a file list from a folder
> with viewer interface.
>
> This objective may require multiple databases and scripting. Again,
> these concepts do not intimidate me since I have extensive experience
> with databases like Access & VB. I just need some helpful advice and
> leads to information to get me up to speed.
>
> Hopefully, someone could give me additional insight on a solution.

Download AlbumFamiy software at http://www.albumsfamily.com to help you