services wanted Urgent: script needed for converting csv data into fixed-width

[brainonastick]

Hi there,

We urgently need a script which will convert csv data exported from Filemaker, into fixed width format for submssion to a government agency. Please contact me at [email protected] if you are interested.

Cheers,

Steven

[Lee Smith]

See if this tread helps

Link

[David McQueen]

Hi Steven,

Lee's post above gives a good description. A couple of things:

1. If you have some sample data, open it up in a word processor or text editor that will show invisibles so you can determine the exact format that you need.

2. Then per the link above, you set up a calculated field to create that format from the filemaker fields. The calculated field is what you export.The big "gotchas" are usually the nature of the padding at the front of each field and the type of number representation expected.

[comment]

There is a better way:

http://fmforums.com/forum/showtopic.php?tid/210527/

[David McQueen]

I really can't comment too much as I am no XML guru.

That link does appear to be a portal to several other links - a great link to start exploring from.

From what I can see it is really granular and does have the effect of removing the process from the database structure itself.

[comment]

removing the process from the database structure

That's precisely the point. It's possible to eliminate practically all calculation fields whose sole purpose is exporting. In fact, you could have the stylesheet do the finding, sorting and summarizing too - but in most cases that is not the most efficient route.

[David McQueen]

That's precisely the point. It's possible to eliminate practically all calculation fields whose sole purpose is exporting. In fact, you could have the stylesheet do the finding, sorting and summarizing too - but in most cases that is not the most efficient route.

Its a long time since I had anything to do with this. At the time I was getting data in, not putting data out. If I remember correctly at that time I used a separate process file. If one has no XML: chops, that strategy would still work and keep the calc fields out of the main program. Not any better or worse in and of itself, just another way to skin the cat.

[comment]

IMHO, it *is* better to keep the logic of external issues in external documents. Consider having to report to multiple insurance companies or government agencies, each with their own specific format and requirements. You'd soon find yourself drowning in calculation fields that have nothing to do with the in-house working of the solution.

Not to mention that if even one of recipients requires a XML format (as they eventually all will), you'll have to dive in and learn the stuff anyway.