Creating a photo file

[Conran]

I work in a store, and we use FM to create bridal registry lists. I would like to add pictures to this list. But I want to create it so that every time I type in the product number, the photo pops up. However I can't just attach the photo directly to the product number, because each week that information is purged and then an excel file is imported into it so that the list remains current. So I would have to recreate the photo's each time. Is there anyway I can create another file that can attach itself through a relationship instead?

[andygaunt]

Hi,

This seems entirely possible.

As long as your photo database has a relationship to the Product number file using the product number as the relationship.

Create your product number database to have this relationship and then place in the picture container field from the photo database on the layout.

Now, when you import the new data from your excel spreadsheet you will see the photos that exist to the matching product numbers.

HTH

[Conran]

Thanks but if the person who updates the product number file totally deletes the file and then imports the new file from excel, wouldn't the images go too? Or are you saying that the images are protected because the they are not actually in the file itself, just referenced there?

[andygaunt]

OK,

The product list file should NOT be allowed to be deleted. The records inside it yes, but not the actual file. Otherwise you would lose the relatioships and any layouts you have.

but if the file is emptied and the new data imported, the product numbers that match those photos (which are stored in their own database) will automatically show in the containers on the layout.

Because, the photo database (the one just for the pictures) has a field in it that is product number that matched that of the product numbers stored in the product database. This field is populated when the photo is created from the product database, because it is the key field for the relationship and you have allow creation of related records checked for the relationship in the product database.

So, in conclusion. You will need.

A Photo database. With fields for

Product Number [ Text field ]

Photo [ Container field ]

A relationship from your product database to photo database

Product Number -> Product Number

with the option allow creation of related records checked.

HTH

[Conran]

Thanks I'll try it!

[cjaeger]

you can do an import with "matching fields". However, with pictures, it is probably better to keep them in a second, related. file.

But there may be some textual info like keywords and additional decriptions in the main file that you may wish to keep.

Next time you import, specify only the fields that need to be updated from excel, and product ID as the matching field. also check add remaining records, do autoenter etc.

[Conran]

thanks, I'll try that too.

[broberts7usa]

This helped a lot! I'm creating a large building (commercial real estate) database with 5 other related DBs (leasing, sales, available space, etc.). I knew I had to have a separate DB to hold all the building images (sometimes several per property) but I just couldn't wrap my brain around it - the learning curve is steep because I just started with FM, not enough time to learn, just plunged right in. All I could remember was having read: "relationships don't work with container fields ..." Then I read a post from Andy Gaunt and got it to work ... Phew!

I still have a couple problems though, because each property can have more than one image, but only one displays on the main property layout (which doubles as a printed brochure). The photos are added on the property main layout and it creates a new record in the images DB - everything works just fine. The images are kept in a separate folder from the DBs and even the new record created in the images stores a reference to the file.

But what if someone finds a better picture for the building (or an alternate view) and adds the new picture to the images folder (all the images are named with the property number ie. 1257im01, 1257im02 etc.) How to change the image on the layout without screwing up the images DB? When I change the image on the property record, to a second/alternate image for that building, it only changes the image record to match the second image, and the info on the first record is lost. I tried making the ImageID (file name eg. 2341im01) require strict validation for a unique name - that doesn't work.

I may need a script? maybe? (an "add picture" button to idiot proof things) to look for the image in the images folder first before attaching it to the record, but then how to add an additional images record if you decide to change the picture to a different one (rather than changing the existing record and leaving the first image floating in the images folder without a record for it ...)

And second question - if I do need a script, how would I go about this? Global fields are still not under my belt but I suspect I may have to stop and learn more about them... "if 1254im01 exists, then create a new record named 1254im02 (or the same name as the filename 1254im02.jpg, whatever ...)

It's making my head spin, please help ... Thanks in advance ...