Importing tif error

[Scott White]

This file format has worked for the 9 years this company has been in
business. And you are right, we import the tab file and some of it is
converted to tables.
All of our other clients are using the same format, pc or mac, and importing
into frame just fine. Just seems that her computer, her framemaker, her
network is causing the problem.
I will suggest to her to clean up her temp directory.
Thanks.
-- 
Scott White
Media Production Manager
Implentation Coordinator
AlaMark Technologies
210-704-8239
swhite at alamark.com


> From: Art Campbell <art.campbell at gmail.com>
> Date: Fri, 3 Nov 2006 13:05:16 -0500
> To: Scott White <swhite at alamark.com>
> Cc: Framers <framers at frameusers.com>
> Subject: Re: Importing tif error
> 
> As far as disk space goes... make sure her temp directory is also free
> of dead files. Note that this isn't the same as memory -- it's space
> for temporary files created when FM processes the .tifs.
> 
> The MIF... I don't use FileMaker. But I'd be really surprised if it
> was generating a proprietary FM/Adobe format file, which is what the
> .MIF is. You mention that it is a comma-delimited file, which also
> isn't right. A tab or comma-delimited file may define a table or a
> database, but that format doesn't map to .MIF all by itself. FM,
> however, can import that kind of file as text and then you can convert
> it to a table...
> 
> So you may want to dig a little deeper and find out exactly what's
> happening with the FileMaker file and how it's being used/imported.
> 
> Art
> 
> On 11/3/06, Scott White <swhite at alamark.com> wrote:
>> Art
>> 1. Since I'm a MAC guy mostly, and She has 60 gb of space availble on her
>> hard drive, it seems to me there is plenty of disck space available. I know
>> on the MAC you can set Frame to what ever memory amount you want.
>> 
>> 2. You are right. Filemaker is generating the mif (tab delimited) file and
>> then import the file by coping into a template.
>> 
>> 3. When I say some images, I mean one time the import error will effect one
>> set of records, you can reimport the same file, and you get a totally
>> different set of images being effected.
>> --
>> Scott White
>> Media Production Manager
>> Implentation Coordinator
>> AlaMark Technologies
>> 210-704-8239
>> swhite at alamark.com
>> 
>> 
>>> From: Art Campbell <art.campbell at gmail.com>
>>> Date: Fri, 3 Nov 2006 12:28:08 -0500
>>> To: Scott White <swhite at alamark.com>
>>> Cc: Framers <framers at frameusers.com>
>>> Subject: Re: Importing tif error
>>> 
>>> OK, three points, or questions.
>>> 1. What happened if/when she freed up some disk space?
>>> 2. And what, exactly, do you mean that she's "importing .... by mif?"
>>> I can't map the words to a FM procedure, so I'm guessing that
>>> FileMaker, not FrameMaker is generating the source file. Is that
>>> correct?
>>> 3. You imply that this only happens with some images. What's the
>>> common thread among the ones that work (or the ones that fail)?
>>> 
>>> Art
>>> 
>>> On 11/3/06, Scott White <swhite at alamark.com> wrote:
>>>> Folks
>>>> I have a client who is importing hi-res .tif images by mif. When she does
>>>> she gets this error for different images: "Cannot store Imagename.tif
>>>> facets; keeping it external.  Try freeing up some disc space. If you are
>>>> importing a graphic, framemaker will import by reference, if you are
>>>> importing a mif file, there may be a mif file error.
>>>> She is importing a mif file generated in filemaker and then importing and
>>>> embedding the graphics. Worked fine up until last week.
>>>> Windows XP Professional Frame 7.1
>>>> 
>>>> Thoughts?????
>>>> Scott White
>>>> Media Production Manager
>>>> Implentation Coordinator
>>>> AlaMark Technologies
>>>> 210-704-8239
>>>> swhite at alamark.com
>>>> 
> -- 
> Art Campbell     
> art.campbell at gmail.com
>   "... In my opinion, there's nothing in this world beats a '52 Vincent
>                and a redheaded girl." -- Richard Thompson
>                              No disclaimers apply.
>                                      DoD 358