Jump to content
Server Maintenance This Week. ×

import graphics


This topic is 8711 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

hi,

this is from the FM technical support:

"Storing external graphics. When using the Import Picture command, you can use the checkbox to "store only a reference to the file. When this option is used, only a thumbnail image is stored in the container field, along with a reference to where to locate the image on disk."

I have a big problem with referenced files - they cannot be found after having copied the database and the images to another computer - is this how FM wants it to be?

does "disk" mean the local disk the database was running when the graphics were imorted with the option "store only a reference to the file"?

thanks for helping

:confused

Link to comment
Share on other sites

quote:

Originally posted by helga:

hi,

this is from the FM technical support:

"Storing external graphics. When using the Import Picture command, you can use the checkbox to "store only a reference to the file. When this option is used, only a thumbnail image is stored in the container field, along with a reference to where to locate the image on disk."

I have a big problem with referenced files - they cannot be found after having copied the database and the images to another computer - is this how FM wants it to be?

does "disk" mean the local disk the database was running when the graphics were imorted with the option "store only a reference to the file"?

thanks for helping

:confused

You do NOT want to use this option. This is an excellent space saver when the files exist on the same disk as when they were setup. However as soon as you copy this database to another computer the references will be lost.

You want to actually store the graphics in the database itself. Although be careful as this makes for a rather large database.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Senior Filemaker Developer

http://www.inthescene.com

mailto:[email protected]

=-=-=-=-=-=-=-=-=-=-=-=-=

Link to comment
Share on other sites

  • Newbies

so what? this is really bad news - how to prevent the large database then? never use filemaker for databases that might contain graphics?

anyway, thanks for answering so quickly

helga

Link to comment
Share on other sites

quote:

Originally posted by helga:

so what? this is really bad news - how to prevent the large database then? never use filemaker for databases that might contain graphics?

anyway, thanks for answering so quickly

helga

This is not really a Filemaker-specific issue. You would have this same issue with any other database. Storing media in database is a pretty new movement and generally requires some serious planning beforehand.

I would need to know more details about your project before I could advise further.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Senior Filemaker Developer

http://www.inthescene.com

mailto:[email protected]

=-=-=-=-=-=-=-=-=-=-=-=-=

Link to comment
Share on other sites

  • Newbies

the project: 2 related databases, one containing objects (houses), the other one documents describing these objects (1:n);

these documents can be scanned photos of the houses, digitized plans, publications about the houses (e.g. in magazines, newspapers, books), letters ...

we want to show thumbnails of the scans for quick browsing and extra layouts for the bigger views, and they should contain the referenced images.

this is shortly what the project is about, I am looking forward to your advise.

thank you

helga

Link to comment
Share on other sites

This topic is 8711 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.