Most of the edi is just a complicated set of text files, usually fixed field, with definitions setting the data layout for various kinds of data records. We do a number of types for financial services. The hardest part is going thru the convoluted definitions and usage and then creating the records. The text files themselves are easier than the underlying model. In our case the data is comprised of many records with different type codes that are inter-related. You can do it in any version of rbase. What we find most difficult is fitting the data to the model and then relating the incoming to existing structures which dont always match. They will want fields you dont have, and will send you data you dont have a place to put, and may not care about. Mark Lindner Lindner & Associates PC 254 Second Ave Needham MA 02494 781 247 1100 Fax 781 247 1143
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, February 25, 2009 6:33 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: General EDI question So then you are just creating text files to send out, and parsing incoming text files, right? Stuff you can do in any (read: older) versions of RBase, right? Karen Then you need to find out what they are loading. My customer is a steel warehouse. They receive steel coils from a mill, then ship them out to whomever the mill tells them to ship them to. So they receive EDI from the mill and send EDI back to the mill after they are shipped. Bernie Lis
