Hello,

I'm using Filemaker Pro 7, trying to migrate to MySQL 4.1 using the FmPro Migrator. I have JPEG images in a container field, not using file references. I import the JPEG images myself and they are stored in the database.

For some reason, when I try to migrate the images to MySQL, it seems that FileMaker is just storing a filename referencing the JPEG files, not the actual data. My size of my images are about 60KB, but when I migrate it, it becomes 28B.

When I import these pictures files, the there's a check box in the import options to import only as a reference to each picture file, and I'm sure that check box is unchecked.

So how can Filemaker turn these image file into actual data in a container field?

Appreciate your help.

Cathy

Sounds like you may not have actually run the full export process. FMPro Migrator uses perl scripts to handle container field contents. There should be an example Image Export Script that came with the product. That will generate a folder full of images from the FM container data, which can then be imported into MySQL or stored separately.

(Make sure you have the Enterprise version of FMPro Migrator.)

I emailed tech support for FMPro Migrator and I was told that I did not need to save the JPEG to my hard disk in order to import it to MySQL. For some reason when I ran the export process, the report file created by FmPro Migrator shows that the container fields weren't really container fields at all.

For example this is part of the max_fieldsize_report I got from FmPro Migrator:

Renamed Field Name Size FileMaker Type Destination Type

peakarea 8 number DOUBLE

peakpic 34 text VARCHAR(255)

peak_text 8008 text VARCHAR(255)

'peakpic' is a container field, but for some reason FmPro Migrator thinks it's a VARCHAR. Perhaps the images in Filemaker is not stored correctly?