FMP7 lets you store arbitary files in container fields.
I would really like to be able to click on the file in FMP and have it 
open in its default application.  But it seems that that does not 
happen.   If you double click the icon, nothing happens.  If you control 
- click it, there is no option for "open".  So I guess all I can do is 
write a script to export the file and then use applescript to open it in 
the finder.

Am I right?

thanks

Luke

Luke Siemaszko <no.spam.for.me@please.com> wrote:

> FMP7 lets you store arbitary files in container fields.
> I would really like to be able to click on the file in FMP and have it
> open in its default application.  But it seems that that does not 
> happen.   If you double click the icon, nothing happens.  If you control
> - click it, there is no option for "open".  So I guess all I can do is
> write a script to export the file and then use applescript to open it in
> the finder.

Nope. Instead of storing the file IN the container, try storing a
reference only. THEN double click and you'll find the document will open
in its native app.

FM seems to assume that any file stored in a container is going to be a
sound or movie file, which will play when double clicked. Otherwise, the
assumption seems to be that files will be stored on a file server and
referenced.  Seems more efficient anyway. References will display faster
and won't bloat file size.

Lynn Allen
--
Allen & Allen Semiotics        www.semiotics.com
FSA Associate       Filemaker Design & Consulting 

Lynn allen wrote:
> Luke Siemaszko <no.spam.for.me@please.com> wrote:
> 
> 
>>FMP7 lets you store arbitary files in container fields.
>>I would really like to be able to click on the file in FMP and have it
>>open in its default application.  But it seems that that does not 
>>happen.   If you double click the icon, nothing happens.  If you control
>>- click it, there is no option for "open".  So I guess all I can do is
>>write a script to export the file and then use applescript to open it in
>>the finder.
> 
> 
> Nope. Instead of storing the file IN the container, try storing a
> reference only. THEN double click and you'll find the document will open
> in its native app.
> 
aaaaaaah!

I wouldn't have expected it to be different.


Thanks