At 08:40 AM 11/12/02 -0000, you wrote: >Dennis McGrath pointed out a few weeks back in reply to another problem the "WRITE var CONTINUE" command will allow you to build a file without CR/LF. Maybe you could utilise that in some way if you haven't already tried it. > >Regards, >Alastair.
Chuck: I was unaware of the "write .var continue" syntax until Dennis' post but found it addressed this problem perfectly. I have an application in RBDOS 6.1a that creates Medicaid billing files in the standard format for electronic transfer. Originally I had a two-step process-- create the file with a series of "write .var" for each identifier and record, then open the file in a word processor and strip out the CR/LFs. Dennis' syntax was was what I was looking for. David >----- Original Message ----- From: "Chuck Novack" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 12, 2002 5:32 AM Subject: EDI without CR/LF Howdy! My client submits a data file to a state agency using zmodem. The old file format was simple. A header record, followed by a series of detail records followed by a footer record. Welcome to the new world of EDI. NEW FILE FORMATS! The new file is (a) significantly more complex and (b) does not allow CR of LF characters. It uses "group" "segment" and "field" identifiers and creates, in essence, 1 file with one rather large (perhaps a 250,000 + byte) record. Mainframers. Ughh. I have dealt with the file complexities (the state will only let me submit 4 test files a week for testing 100's of data elements), but the lack of Carriage Returns and Line Feeds has not been resolved for production purposes. My client is very happy with version R:Base 6.0 for DOS (running in a DOS Window under Win 98 in a Netware environment). He does not want to upgrade. Instead of writing out records, I have had success in appending the variable string to a "work variable" defined as a NOTE field. It works well ... but I have a 4K record size limit. OK for testing, but not production. When I switch it to a VAR CHAR it fails miserably. I've messed around with several alternatives ... Does anybody have an approach that is clean? I appreciate your input! Chuck [EMAIL PROTECTED] ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
