Graphic Image Storage in FMP 6 
Author Message
 Graphic Image Storage in FMP 6
I have just browsed through the FMP site data on their new 6.0
version, and it is not clear to me how image files are stored.

Is it possible in this new version to store a reference to an image
stored in another file? Could the images be on a CD, or other location
identified in a field of the database?

If another viewing program is launched to see the image, how is the
user re-directed back to the FMP database?

Bill Parker



Thu, 10 Feb 2005 03:05:19 GMT
 Graphic Image Storage in FMP 6



Quote:
> I have just browsed through the FMP site data on their new 6.0
> version, and it is not clear to me how image files are stored.

> Is it possible in this new version to store a reference to an image
> stored in another file? Could the images be on a CD, or other location
> identified in a field of the database?

Yes, with the following caveat: if the CD is removed or if the file
containing the image file is relocated or if the filename of image file is
changed, the reference is broken.  You have to reinsert the CD, replace the
folder or restore the original name of the image file to fix the reference.

The import command can now be used to update existing records from a folder
of files as well as import new records from a folder of files, which makes
it easier than ever to restore broken references when you need to move files
around.  In order to do this you have to nominate one field as a match
field.  Since the only real choices are filename and filepath (and filename
is part of filepath), editing filenames is still a problem.  It would have
been nice if we had been able to use creation date and time too..

Quote:
> If another viewing program is launched to see the image, how is the
> user re-directed back to the FMP database?

In v6, command-clicking the filepath (which can be automatically imported
when the image is imported, along with filename and thumbnail) will
automatically open the original image in the application that created it,
but once you leave filemaker, there is no simple way of bringing users back
(other than to instruct them to hide the graphics application which should
bring filemaker back to the front).

However, images that are referenced rather than imported will still display
in a container field in filemaker the same way as an imported image, so
there is really no reason to leave filemaker in the first place.  You can do
all kinds of cool things this way: for example, create a scripted button
that tests screen size and goes to a different layout on the basis of that.
Each layout would be set to maximise, and have the container field resized
to exactly fit those proportions.  Format the container field to reduce
(only if larger than the window), centre and maintain its original
proportions.  Then format the container field as a button that returns to
the previous layout.

--
Bridget Eley



Thu, 10 Feb 2005 05:18:00 GMT
 Graphic Image Storage in FMP 6

Quote:



> > I have just browsed through the FMP site data on their new 6.0
> > version, and it is not clear to me how image files are stored.

> > Is it possible in this new version to store a reference to an image
> > stored in another file? Could the images be on a CD, or other location
> > identified in a field of the database?

> Yes, with the following caveat: if the CD is removed or if the file
> containing the image file is relocated or if the filename of image file is
> changed, the reference is broken.  You have to reinsert the CD, replace the
> folder or restore the original name of the image file to fix the reference.

> The import command can now be used to update existing records from a folder
> of files as well as import new records from a folder of files, which makes
> it easier than ever to restore broken references when you need to move files
> around.  In order to do this you have to nominate one field as a match
> field.  Since the only real choices are filename and filepath (and filename
> is part of filepath), editing filenames is still a problem.  It would have
> been nice if we had been able to use creation date and time too..

> > If another viewing program is launched to see the image, how is the
> > user re-directed back to the FMP database?

> In v6, command-clicking the filepath (which can be automatically imported
> when the image is imported, along with filename and thumbnail) will
> automatically open the original image in the application that created it,
> but once you leave filemaker, there is no simple way of bringing users back
> (other than to instruct them to hide the graphics application which should
> bring filemaker back to the front).

> However, images that are referenced rather than imported will still display
> in a container field in filemaker the same way as an imported image, so
> there is really no reason to leave filemaker in the first place.  You can do
> all kinds of cool things this way: for example, create a scripted button
> that tests screen size and goes to a different layout on the basis of that.
> Each layout would be set to maximise, and have the container field resized
> to exactly fit those proportions.  Format the container field to reduce
> (only if larger than the window), centre and maintain its original
> proportions.  Then format the container field as a button that returns to
> the previous layout.

Bridget,

I can't thank you enough for the very helpful response you posted to
my query.

I downloaded the trial version of release 6.0, and have been
experimenting succesfuly.

I hadn't posted all of the reasons for wanting a variable drive
letter, and source folders, as I didn't want to bore people with too
many details. Here is what I needed to do:

I am working on photographic databases for an historical society, as a
volunteer. The society has over 70,000 photos, ranging from early
glass plate negatives and Daguerrotypes up to more contemporary
pictures.

We are scanning the images at high resolution for achival purposes,
and to be searchable by patrons. We save them on CD-ROMs into files by
subject, or by photographer, or by other categories.

We then make databases to allow entry of information about the images,
to be searchable by genealogists, historians, newspaper writers, etc.

Since the drive letters of the CD-ROM's are not always the same on
machines used by patrons, it is convenient to be able to change the
drive source and pathname for the stored images.

I finally wound up creating fields for these, and concatenating them
into one field labelled "source", I then had to make a copy if that
field for the purpose of launching the program under which the image
was created, if that is needed.

I really like the improved utilities in version 6 for importing, and
for launching other programs. I had tried using plug-in third party
programs, but greatly prefer having it all in Filemaker.

Thanks, again, for your help.

Bill Parker



Sat, 19 Feb 2005 03:05:45 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. Help:Saving Graphic Image Into A BLOB Graphic Field In Paradox Table

2. CDML COMMAND:[fmp-linkfirst] [fmp-linknext] [fmp-linklast] [fmp-linkprevious]

3. sending graphics in FMP web page

4. Graphic filter JPEG (for FMP 3.0.5)

5. Help! FMP 4.0 Web graphic distortion

6. FMP 6 No Longer Supports PDF Graphic Format

7. Graphics file storage in database - which database?

8. Graphics file storage in database - which database?

9. Paradox 8 graphic images with MS SQL

10. Displaying graphic images via SQL 7 db

11. Store image/graphic in SQL server

12. Displaying graphic images via SQL 7 db


 
Powered by phpBB® Forum Software