On 10/1/09 11:36 AM, "Corn Walker" <[email protected]> wrote in whole or in part:
> On Oct 1, 2009, at 11:24 AM, Bob Minteer wrote: > >> If you do this, keep in mind that the output format will be UTF-16 >> (not UTF-8). Some progs have no problem with this... And some do. > > You can choose a different output file character set. This is > accomplished by using the standard "Export Records" command to export > a found set instead of the "Export Field Contents" command. Your found > set contains only a single record and your export order includes only > the previously recommended global field. Choose the "Tab-Separated > Text" file format and on the ensuing dialog select your output file > character set. Yes! Just keep in mind the "return-in-field", gets converted to VT (vertical tab) and the TAB gets converted to space when you export as Tab-delimited. That is because this format uses "return" as the row ender (even though you have one row) and the "tab" as the field delimiter (even though you only have one field). If you need these characters "as-is", then XML is a great choice. > I might still use XML/XSLT but this method also works in a pinch. I've worked "EDI" with calcs/scripts (way long ago, probably FMP 3/4.1 days) and with XML. Maintaining the calcs is much harder than revising an XSLT. But maybe that's just me. <smile /> Beverly > Cheers, > -corn > > > Corn Walker > The Proof Group > http://proofgroup.com/
