Adam,

I would think the format of the application files is going to depend in
large part on what tools you are using for translation.  Some commercial
translators are designed to use CSV file formats, others prefer flat,
positional files and some are designed to read and write directly to
database files/tables.  As for qualifiers and references, I would think
it would be easier to have qualifiers and references in the application
files rather than separate fields for every type of reference
(especially since, in some cases, there can be a lot of possible
qualifiers).  My favorite approach as always been to say: what's the
easiest way to accomplish what I need to do?

The key question is really how do you arrange the data in the
application files and I would expect that would depend largely on the
arrangement of the files/data in the application itself.

Best regards,
Bill Chessman
Inovis(tm)

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of
Becker, Adam
Sent: Tuesday, December 05, 2006 9:52 AM
To: [email protected]
Subject: [EDI-L] Application File Formats

Hello All,
 
I'm hoping to get your input on application files, does any body know of
any best practices for defining the format for these?  Is delimited or
positional better?  Should you use qualifiers for things like references
or just have a field for every type of reference you could possibly
expect?  Should you only have one line in the file for each line in the
database?  Any input/advice/past mistakes/etc. would be very much
appreciated.
 
 
Thanks,

Adam

This email message and any attachments are for the sole use of the
intended recipient(s). This email and any attachments may contain
confidential, privileged or otherwise protected information, including
legal protection under the Health Insurance Portability and
Accountability Act (HIPAA). If you are not the above named intended
recipient, you are hereby notified that any use, disclosure, printing,
copying, or distribution of this email or attachments is strictly
prohibited and may subject you to criminal and/or civil penalties. If
you have received this email in error, please immediately notify the
sender by telephone or reply email and destroy this email



[Non-text portions of this message have been removed]



...
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work:
<JOBS> IS REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links





...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

Reply via email to