exporting to a text file

I have mhtml code that I want stored in a field.  Reason being, I can
do a replace to use this same code to make custom documents for
multiple clients.  I copy and paste from notepad to filemaker, but
when I try to export the code from the calculation that does the
replace, it doesn't work.  I notice in the original cut and paste,
there are definite line breaks, but on the exported text from
filemaker (using Export Field Contents script step), there are no line
breaks...only little squares.  This exported code renders nothing in
IE.  Interestingly, if I were to copy and paste the calculation text
from filemaker to a new notepad document and save as .mht, it works

"EP" <ericp023@gmail.com> schreef in bericht 
news:70c127db-5228-493f-bcde-06d35130c6d0@e39g2000hsf.googlegroups.com...
>I have mhtml code that I want stored in a field.  Reason being, I can
> do a replace to use this same code to make custom documents for
> multiple clients.  I copy and paste from notepad to filemaker, but
> when I try to export the code from the calculation that does the
> replace, it doesn't work.  I notice in the original cut and paste,
> there are definite line breaks, but on the exported text from
> filemaker (using Export Field Contents script step), there are no line
> breaks...only little squares.  This exported code renders nothing in
> IE.  Interestingly, if I were to copy and paste the calculation text
> from filemaker to a new notepad document and save as .mht, it works
> fine.  Anybody know the reason for this and if it is fixable?

First of all, it is not very sound practice to rely on a copy and paste. 
Certainly when there multiple users on your system active. You never know 
what might happen with your clipboard. The copy/paste problem you describe 
is known. I'm not sure this is a bug, I tend to think so. But opinions vary. 
Since Filemaker uses it's own way to display the information needed. The way 
around is using plug-in. The free File Toolbox is my prefered choice. The 
payware from troi (Troi File plugin) is very good. You can use it without 
paying, but it quits working after 30 minutes (or was it 45 minutes) after 
first activation. You have to restart filemaker completely to get another 45 
minutes of activity.

Keep well, Ursus 

In article
<70c127db-5228-493f-bcde-06d35130c6d0@e39g2000hsf.googlegroups.com>, EP
<ericp023@gmail.com> wrote:

> I have mhtml code that I want stored in a field.  Reason being, I can
> do a replace to use this same code to make custom documents for
> multiple clients.  I copy and paste from notepad to filemaker, but
> when I try to export the code from the calculation that does the
> replace, it doesn't work.  I notice in the original cut and paste,
> there are definite line breaks, but on the exported text from
> filemaker (using Export Field Contents script step), there are no line
> breaks...only little squares.  This exported code renders nothing in
> IE.  Interestingly, if I were to copy and paste the calculation text
> from filemaker to a new notepad document and save as .mht, it works
> fine.  Anybody know the reason for this and if it is fixable?

Exported files use "line breaks" / returns to indicate new records,
so
when exporting data FileMaker will automatically replace any return
characters within Text fields with a vertical tab. 

It's not a bug  and it's not "fixable". It's standard practice in
most
applications that export data and is part of the "established" format
for 'tab delimited' and CSV format text files.

There are some work-arounds though:

1.   Use a plug-in that can export whatever format you want.

2.   Have a Calculation field that takes the original pasted data and 
     replace the return characters with something unique like "*-*".
     You then export this field instead and once outside of FileMaker 
     again you can re-replace the "*-*" with a return character using
     Word, Notepad or whatever.

3.   Separate each line of you mhtml code into individual records.
     This could be done by pasting the code into a Global Text field
     and then running a script to parse the text into separate records.
     You then export multiple records to get you original mhtml code
     back again, complete with return characters.

I don't know anything about mhtml code (I've never even heard of it
before), but in normal HTML code the returns are irrelevant anyway
(other than making it easier for us humans to read), but the vertical
tabs replacements might cause a small problem so they would need
replacing.



Helpful Harry                   

On Thu, 13 Mar 2008 09:03:45 +1300, Helpful Harry
<helpful_harry@nom.de.plume.com> wrote:

>In article
><70c127db-5228-493f-bcde-06d35130c6d0@e39g2000hsf.googlegroups.com>,
EP
><ericp023@gmail.com> wrote:
>
>> I have mhtml code that I want stored in a field.  Reason being, I can
>> do a replace to use this same code to make custom documents for
>> multiple clients.  I copy and paste from notepad to filemaker, but
>> when I try to export the code from the calculation that does the
>> replace, it doesn't work.  I notice in the original cut and paste,
>> there are definite line breaks, but on the exported text from
>> filemaker (using Export Field Contents script step), there are no line
>> breaks...only little squares.  This exported code renders nothing in
>> IE.  Interestingly, if I were to copy and paste the calculation text
>> from filemaker to a new notepad document and save as .mht, it works
>> fine.  Anybody know the reason for this and if it is fixable?
>
>Exported files use "line breaks" / returns to indicate new
records, so
>when exporting data FileMaker will automatically replace any return
>characters within Text fields with a vertical tab. 
>
>It's not a bug  and it's not "fixable". It's standard practice in
most
>applications that export data and is part of the "established"
format
>for 'tab delimited' and CSV format text files.
>
>There are some work-arounds though:
>
>1.   Use a plug-in that can export whatever format you want.
>
>2.   Have a Calculation field that takes the original pasted data and 
>     replace the return characters with something unique like
"*-*".
>     You then export this field instead and once outside of FileMaker 
>     again you can re-replace the "*-*" with a return character
using
>     Word, Notepad or whatever.
>
>3.   Separate each line of you mhtml code into individual records.
>     This could be done by pasting the code into a Global Text field
>     and then running a script to parse the text into separate records.
>     You then export multiple records to get you original mhtml code
>     back again, complete with return characters.
>
>I don't know anything about mhtml code (I've never even heard of it
>before), but in normal HTML code the returns are irrelevant anyway
>(other than making it easier for us humans to read), but the vertical
>tabs replacements might cause a small problem so they would need
>replacing.

Harry,

"mhtml" is a Microsoft proprietary file type which basically creates
a
self-contained single-file archive of a Web page by embedding the
images et cetera.  Its main practical use is for sending Web pages as
email attachments, and even then only for pages that can't be
hyperlinked.

Anyway, on the OP: couldn't he just specify different encoding during
the export?  UTF-8 supports Unix line breaks (LF only).

-- 
FW

FileMaker Pro 8.5 on Windows XP Pro SP2
FileMaker Server 8.0 on Windows 2003 Server