dbTalk Databases Forums  

Storing Big JPEG Images In a FileMaker database

comp.databases.filemaker comp.databases.filemaker


Discuss Storing Big JPEG Images In a FileMaker database in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Anne DeBlois
 
Posts: n/a

Default Storing Big JPEG Images In a FileMaker database - 11-09-2005 , 02:36 PM






Hi,

I inserted 44 high-quality JPEG pictures, each one between 1 and 2 MB in
size, into a FileMaker database. I expected an 80 or 100-MB file, but I
ended up with a huge, 500-MB database instead. I am sorry for being
graphically-impaired (especially with FileMaker), but are JPEG pictures
always uncompressed when inserted into a FileMaker database? Or is there
something I must do to keep the compression?

Thanks in advance,

Anne (from Canada)



Reply With Quote
  #2  
Old   
Leon Obers
 
Posts: n/a

Default Re: Storing Big JPEG Images In a FileMaker database - 11-09-2005 , 03:32 PM








Anne DeBlois wrote:

Quote:
I inserted 44 high-quality JPEG pictures, each one between 1 and 2 MB in
size, into a FileMaker database. I expected an 80 or 100-MB file, but I
ended up with a huge, 500-MB database instead. I am sorry for being
graphically-impaired (especially with FileMaker), but are JPEG pictures
always uncompressed when inserted into a FileMaker database? Or is there
something I must do to keep the compression?
Better not to store the images inside the filemaker application itself,
only do give a "link" within the containerfield to the directory the
images are stored.
See the check/uncheck square when choosing a picture datafile to match
the containerfield to include the picture or only give a link.


--
Vr.groet - regards, Léon Obers

Reacties per mail, vervang "invalid" door "cc" in het adres.
Reactions by mail, exchange "invalid" by "cc" within address.



Reply With Quote
  #3  
Old   
Gregory Weston
 
Posts: n/a

Default Re: Storing Big JPEG Images In a FileMaker database - 11-09-2005 , 03:42 PM



In article <C7tcf.14584$1L3.608057 (AT) news20 (DOT) bellglobal.com>,
"Anne DeBlois" <adNOeblSPAMois (AT) dsdinternational (DOT) net> wrote:

Quote:
Hi,

I inserted 44 high-quality JPEG pictures, each one between 1 and 2 MB in
size, into a FileMaker database. I expected an 80 or 100-MB file, but I
ended up with a huge, 500-MB database instead. I am sorry for being
graphically-impaired (especially with FileMaker), but are JPEG pictures
always uncompressed when inserted into a FileMaker database? Or is there
something I must do to keep the compression?
I would recommend just storing references to the images unless you know
you need to embed them for some reason. Aside from the data inflation
you've observed, it can have a huge impact on your backup process to not
have to back up all of the pictures again every time a record changes.

--
Goal 2005: Convincing James Hetfield to cover the Strawberry Shortcake
"Are You Berry Berry Happy?" song.


Reply With Quote
  #4  
Old   
ursus.kirk
 
Posts: n/a

Default Re: Storing Big JPEG Images In a FileMaker database - 11-10-2005 , 05:11 AM



Anne

I hereby repost an answer I wrote a couple of weeks ago. Concerning the same
question. My answer was to implement referenced images only. Here is how to
do that.

Quote:
Filemaker is not a picture/pdf/wav file storage program.

Oh.. then why does it have features like "insert picture", "insert
sound", "insert file" and "insert object"?
dunno, to store very small images??

Quote:
For my pics I always use a calculated container,

Could you please describe briefly how you created the calculated
container (what kind of formula?) and how you are using it?

here we go:
FileMaker 7&8 offers the "Insert Picture/QuickTime/File" script commands to
place data into a container field. However, these script steps are limited
in that they must explicitly identify the particular file to be imported.
(You cannot express a path using a calculated value.)

If you want to dynamically control the contents of a container field, you
can instead use either the "Set Field" script step, or auto-enter options.
Both will accept a calculated value as a parameter.

The calculation must result in a string representing the file path in the
same format used by the "Insert Picture/QuickTime/File" script commands.
(Just an in any calculation, literals must be enclosed in quotes.) Supported
formats for the pathname include the following:

file:directoryName/fileName
filemac:/volumeName/directoryName/fileName
filewin:/driveletter:/directoryName/fileName
filewin://computerName/shareName/directoryName/fileName
image:directoryName/fileName
imagemac:/volumeName/directoryName/fileName
imagewin:/driveletter:/directoryName/fileName
imagewin://computerName/shareName/directoryName/fileName
movie:directoryName/fileName
moviemac:/volumeName/directoryName/fileName
moviewin:/driveletter:/directoryName/fileName
moviewin://computerName/shareName/directoryName/fileName

For example:

Set Field [Personnel::idPhoto; "imagewin:/D:/Photos/" &
Personnel::employeeID & ".jpg"]

will set the conatinerfield idPhoto to show "23456.jpg" from the D:/Photos
directory, when
employeeID is 23456.

When a container field is set using this method, the files are always stored
"by reference" only. They are not copied into the FileMaker database file.
If the original file is moved or renamed, FileMaker will display "the file
cannot be found" in the container field. If the original file is modified,
the new contents will be shown when it is updated.

Calculations may also reference container fields. for example, if you import
a picture "rose.gif" into field, "myImage" then the calculation

checkPic (calculation, text result) = TestDB::myImage

will return:

- "rose.gif" if you imported the picture from disk and stored it within
FileMaker
- "?" if you placed it into the field via the clipboard
- "size: 630,240
image:../../My Documents/My Pictures/rose.gif
imagewin:/D:/My Documents/My Pictures/rose.gif" if you imported it from
disk and stored only a reference to the file.

Using both techniques together, you could handle a situation where a
directory of images had to be moved or converted to a different format,
without re-importing them. For example:

Substitute ( Catalog::ProductImage; "/images/"; "/archived/")

If all the images referenced in your file had been moved to the "archived"
directory.

Ursus

"Anne DeBlois" <adNOeblSPAMois (AT) dsdinternational (DOT) net> schreef in bericht
news:C7tcf.14584$1L3.608057 (AT) news20 (DOT) bellglobal.com...
Quote:
Hi,

I inserted 44 high-quality JPEG pictures, each one between 1 and 2 MB in
size, into a FileMaker database. I expected an 80 or 100-MB file, but I
ended up with a huge, 500-MB database instead. I am sorry for being
graphically-impaired (especially with FileMaker), but are JPEG pictures
always uncompressed when inserted into a FileMaker database? Or is there
something I must do to keep the compression?

Thanks in advance,

Anne (from Canada)




Reply With Quote
  #5  
Old   
Anne DeBlois
 
Posts: n/a

Default Re: Storing Big JPEG Images In a FileMaker database - 11-10-2005 , 07:24 AM




"Gregory Weston" <uce (AT) splook (DOT) com> a écrit dans le message de news:
uce-2A498E.16420809112005 (AT) comca...a.giganews.com...
Quote:
I would recommend just storing references to the images unless you know
you need to embed them for some reason. Aside from the data inflation
you've observed, it can have a huge impact on your backup process to not
have to back up all of the pictures again every time a record changes.
Oops! I forgot to mention that the images are stored in a file that is
linked to the main database.

Anne




Reply With Quote
  #6  
Old   
Anne DeBlois
 
Posts: n/a

Default Re: Storing Big JPEG Images In a FileMaker database - 11-10-2005 , 07:25 AM



Hi ursus kirk,

Thank you! I'll see what I can do.

Anne

"ursus.kirk" <secret (AT) nowhere (DOT) com> a écrit dans le message de news:
43732ad1$0$82065$dbd4f001 (AT) news (DOT) wanadoo.nl...
Quote:
Anne

I hereby repost an answer I wrote a couple of weeks ago. Concerning the
same question. My answer was to implement referenced images only. Here is
how to do that.


Filemaker is not a picture/pdf/wav file storage program.

Oh.. then why does it have features like "insert picture", "insert
sound", "insert file" and "insert object"?

dunno, to store very small images??


For my pics I always use a calculated container,

Could you please describe briefly how you created the calculated
container (what kind of formula?) and how you are using it?


here we go:
FileMaker 7&8 offers the "Insert Picture/QuickTime/File" script commands
to
place data into a container field. However, these script steps are limited
in that they must explicitly identify the particular file to be imported.
(You cannot express a path using a calculated value.)

If you want to dynamically control the contents of a container field, you
can instead use either the "Set Field" script step, or auto-enter options.
Both will accept a calculated value as a parameter.

The calculation must result in a string representing the file path in the
same format used by the "Insert Picture/QuickTime/File" script commands.
(Just an in any calculation, literals must be enclosed in quotes.)
Supported
formats for the pathname include the following:

file:directoryName/fileName
filemac:/volumeName/directoryName/fileName
filewin:/driveletter:/directoryName/fileName
filewin://computerName/shareName/directoryName/fileName
image:directoryName/fileName
imagemac:/volumeName/directoryName/fileName
imagewin:/driveletter:/directoryName/fileName
imagewin://computerName/shareName/directoryName/fileName
movie:directoryName/fileName
moviemac:/volumeName/directoryName/fileName
moviewin:/driveletter:/directoryName/fileName
moviewin://computerName/shareName/directoryName/fileName

For example:

Set Field [Personnel::idPhoto; "imagewin:/D:/Photos/" &
Personnel::employeeID & ".jpg"]

will set the conatinerfield idPhoto to show "23456.jpg" from the D:/Photos
directory, when
employeeID is 23456.

When a container field is set using this method, the files are always
stored
"by reference" only. They are not copied into the FileMaker database file.
If the original file is moved or renamed, FileMaker will display "the file
cannot be found" in the container field. If the original file is modified,
the new contents will be shown when it is updated.

Calculations may also reference container fields. for example, if you
import
a picture "rose.gif" into field, "myImage" then the calculation

checkPic (calculation, text result) = TestDB::myImage

will return:

- "rose.gif" if you imported the picture from disk and stored it within
FileMaker
- "?" if you placed it into the field via the clipboard
- "size: 630,240
image:../../My Documents/My Pictures/rose.gif
imagewin:/D:/My Documents/My Pictures/rose.gif" if you imported it from
disk and stored only a reference to the file.

Using both techniques together, you could handle a situation where a
directory of images had to be moved or converted to a different format,
without re-importing them. For example:

Substitute ( Catalog::ProductImage; "/images/"; "/archived/")

If all the images referenced in your file had been moved to the "archived"
directory.

Ursus

"Anne DeBlois" <adNOeblSPAMois (AT) dsdinternational (DOT) net> schreef in bericht
news:C7tcf.14584$1L3.608057 (AT) news20 (DOT) bellglobal.com...
Hi,

I inserted 44 high-quality JPEG pictures, each one between 1 and 2 MB in
size, into a FileMaker database. I expected an 80 or 100-MB file, but I
ended up with a huge, 500-MB database instead. I am sorry for being
graphically-impaired (especially with FileMaker), but are JPEG pictures
always uncompressed when inserted into a FileMaker database? Or is there
something I must do to keep the compression?

Thanks in advance,

Anne (from Canada)






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.