# FileMaker Export Records

**URL:** <https://the.fmsoup.org/t/filemaker-export-records/3054>\
**Category:** Questions\
**Tags:** community\
**Created:** [August 17, 2022, 4:03pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054 "2022-08-17T16:03:17Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [August 17, 2022, 4:03pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/1 "2022-08-17T16:03:17Z")

</div>

I noticed that when doing an export from FileMaker to CSV, and then opening that CSV up in, say, BBEDIT, there are lots of unrecognized characters (possibly the same one).  
I selected UTF-8 for the export (and tried others, too) so I'm not sure what the problem is.  
How can I get just the text output?  
Thanks,

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [August 17, 2022, 4:21pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/2 "2022-08-17T16:21:14Z")

</div>

BBEdit is simply showing you what is there. With the CSV open in BBEdit, to find out what the character is, select it, then go to Window -\> Palettes -\> Character Inspector.

To find out more about plain text, watch this video

[![](https://img.youtube.com/vi/_mZBa3sqTrI/maxresdefault.jpg "Plain Text - Dylan Beattie - NDC Oslo 2021") ](https://www.youtube.com/watch?v=_mZBa3sqTrI)

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [August 17, 2022, 4:40pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/3 "2022-08-17T16:40:58Z")

</div>

Thanks @Malcolm! (That was also a great BBEdit tip!)

The issue is why the character (Unicode 000B) won't export as the character itself.

Not sure how to remedy this from the atomic "Export Records" script step.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [August 17, 2022, 4:46pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/4 "2022-08-17T16:46:53Z")

</div>

Unicode 000B is the line tab or vertical tab.

~~Tab~~ Return characters pasted into text fields get silently converted to vertical tabs. ~~You can type them in by using option-tab on the Mac, I forget the windows key combo.~~

Of course, in BBEdit you can search for unicode characters and replace them all with \t.

_thanks for the correction @bdbd_

---

<div class="post-metadata">

**Author:** ![bdbd](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/bdbd/32/620_2.png) [@bdbd](https://the.fmsoup.org/u/bdbd)\
**Post date:** [August 17, 2022, 5:07pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/5 "2022-08-17T17:07:03Z")

</div>

Sorry @Malcolm… but that's incorrect. Character 000B, the vertical tab, replaces the newline and return characters in both tab delimited and in comma separated value files. Tab characters in tab delimited files are replaced by spaces. They are not replaced in comma separated value files.

---

<div class="post-metadata">

**Author:** ![mipiano](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/mipiano/32/1074_2.png) [@mipiano](https://the.fmsoup.org/u/mipiano)\
**Post date:** [August 17, 2022, 6:25pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/6 "2022-08-17T18:25:25Z")

</div>

@OliverBarrett  
Did you try Windows-1252 instead of UTF-8 too?

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [August 17, 2022, 6:40pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/7 "2022-08-17T18:40:13Z")

</div>

Yep.  
I think it's a BBEDIT thing. The file opens OK in TextEdit.  
Thx

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [August 17, 2022, 10:37pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/8 "2022-08-17T22:37:43Z")

</div>

> [@OliverBarrett](#):
>
> I think it's a BBEDIT thing. The file opens OK in TextEdit.

Different approaches. TextEdit is assuming that you are engaged with word processing activities and that a vertical tab is delineating white space. A good assumption in this case. BBEdit is assuming that a CSV file is a data record and it ensures that each record is displayed on a single line.

You can copy and paste between the two. Exactly the same text, different handling of white space characters.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [August 18, 2022, 6:06pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/9 "2022-08-18T18:06:19Z")

</div>

Thanks

---

<div class="post-metadata">

**Author:** ![kerplop](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@kerplop](https://the.fmsoup.org/u/kerplop)\
**Post date:** [August 24, 2022, 5:18pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/10 "2022-08-24T17:18:04Z")

</div>

I don't know if this adds any info to this particular problem, but I needed to write a file with both CRs and LFs, and BBEdit would assume both were line endings and convert them both to LFs. I called their Help desk and was informed that this was the default behavior and that I couldn't change it. (Which I thought was odd for a text editor.) Maybe they treat the vertical tab similarly.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [August 24, 2022, 5:47pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/11 "2022-08-24T17:47:31Z")

</div>

In my case, BBEDit suggested I do a Reg-Ex replace on the problem character.

Thanks

---

<div class="post-metadata">

**Author:** ![bdbd](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/bdbd/32/620_2.png) [@bdbd](https://the.fmsoup.org/u/bdbd)\
**Post date:** [August 25, 2022, 4:23am UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/12 "2022-08-25T04:23:49Z")

</div>

That doesn't look right. BBEdit doesn't convert file data. Furthermore, you can specify the line ending of files. Unix (LF), Mac (CR) and Windows (CRLF) are all supported. This is selectable below the horizontal scroll bar.

---

<div class="post-metadata">

**Author:** ![kerplop](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@kerplop](https://the.fmsoup.org/u/kerplop)\
**Post date:** [November 16, 2022, 11:02pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/13 "2022-11-16T23:02:59Z")

</div>

But have you tried using both in a file? In my case, I'm using Applescript to compose and write the text file out of Filemaker. It contains one CR, and LFs thereafter. The target file format demands one CR near the beginning; ensuing line breaks must be LFs. BBEdit does not honor the distinction.

---

<div class="post-metadata">

**Author:** ![bdbd](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/bdbd/32/620_2.png) [@bdbd](https://the.fmsoup.org/u/bdbd)\
**Post date:** [November 17, 2022, 12:53am UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/14 "2022-11-17T00:53:11Z")

</div>

Just to be sure I understand, you are saying a file must be formatted as follows?

CR  
blah blah blah LF  
blah blah blah LF  
blah blah blah LF  
blah blah blah LF  
EOF

Did I get this right?

---

<div class="post-metadata">

**Author:** ![kerplop](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@kerplop](https://the.fmsoup.org/u/kerplop)\
**Post date:** [November 23, 2022, 11:23pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/15 "2022-11-23T23:23:48Z")

</div>

Almost:

blah blah CR  
blah blah blah LF  
blah blah blah LF  
blah blah blah LF  
blah blah blah LF  
EOF

The first blah blah determines the version of the tag file. Then the LFs indicate line breaks in the text, not CRs.

Thanks,

k

---

<div class="post-metadata">

**Author:** ![bdbd](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/bdbd/32/620_2.png) [@bdbd](https://the.fmsoup.org/u/bdbd)\
**Post date:** [November 24, 2022, 12:48am UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/16 "2022-11-24T00:48:33Z")

</div>

I understand. This definitely means no text editor I know of can output the file you want to output because the line endings are inconsistent. All text editors I know of will output the same line ending for each line of a given file. They may give you the option of selecting a line ending, but that selection will be applied to all lines in the file.

Another option, at least in FileMaker 19, is to use the file editing script steps.

Hope this helps.

---

<div class="post-metadata">

**Author:** ![kerplop](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@kerplop](https://the.fmsoup.org/u/kerplop)\
**Post date:** [December 5, 2022, 11:04pm UTC](https://the.fmsoup.org/t/filemaker-export-records/3054/17 "2022-12-05T23:04:02Z")

</div>

Yeah, it's pretty weird. I could write a correct file out of FMP using Applescript; I just couldn't edit it and have the CR and LFs remain as-is with a word processor (BBEdit).
