I would recommend building your EDI file in a global field and then exporting the field contents of the global field to a text file.
You can control all of your padding and such in the script and through some of the custom functions already available at Brian Dunnings site. 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. If the intended recipient of the EDI file can only take in UTF-8 text then you can buy a TROI file plug in to output the data in the proper format (I believe). My database retrieves remittance advice via EDI data several times a week (native... No plug-in involved). It comes to us as UTF-8. Regards... Bob Minteer On 10/1/09 9:06 AM, "Peter Buchanan" <[email protected]> wrote: > Can anyone offer advice and direction on exporting data from FM10 (I am > thinking in CSV format) and from that output, creating a flat text file with > definite fixed widths for each field. This file is then used for EDI with > other service providers. > > Is it possible / feasible doing this in FM itself (unused spaces would have to > be filled with blanks) , or can anybody recommend software that will do this > I have heard of translator² software? > > Many thanks > Peter > > >
