Hi Chuck,

Apologies for the late reply, I don't use much R:Base these days but still watch this list every now and then.
I used to load date into R:Base in a variety if formats eg. a C/R and no L/F, no last end-of-line character, 2 end-of-line characters at the end of the file, no final end-of-line characters, strange date formats etc. Having to use The mighty SQL Server (Wash your mouth in Jayes Fluid) life becomes quite straightforward as you are unlikely to automate the loading of data from other non Microsoft applications.

I now adopt the policy of passing all files through a custom executable to convert the file to a standard format. If you use Delphi or C consol programs they are tiny, very fast and easy to right.

Ian


At 05:32 12/11/2002, you wrote:
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/

================================================
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/

Reply via email to