Ian, I guess it depends on the data's destination. I did a quick and dirty test loading into Excel w/o problem.
>It does not understand that ''' = ' rule. Doesn't apply here. Quotes should be set to be compatible with the receiving DB. Ben Petersen On 1 Feb 2002, at 11:36, Ian Stone wrote: > Ben, > > I've been there. You get in a big mess with quotes. I guess Phil is > trying to fire his data into a Microsoft database which get horribly > confused when there is a quote in the data. It does not understand that > ''' = ' rule. > > Ian > > At 16:31 31/01/2002 +0000, Ben Petersen wrote: > >Phil, > > > >I _think_ Ian trying to skip Gateway. To build on his idea, another > >approach _might_ be: > > > >Set v zDelim = (char(9)) > >Set delimit = .zDelim > > > >output FileName > >unload data from BigOlTable as ascii > >output screen > > > >Set delimit = ',' > > > > > >Ben Petersen > > > > > >On 31 Jan 2002, at 18:07, Phil Nolette (NCS Group, Inc.) wrote: > > > > > Ian, > > > Thanks for the reply. I have no problem with exporting the data 1 row = > > > (390 characters/text). I am using Gateway Export ASCII TAB. The problem I > > > am having is that I have 150,000 rows of data in that table and have to > > > break down the export into 5,000 rows of export data for it to finish > > > writing the file. > > > > > > Since I posted this message, I have gone into Control Panel - Performance - > > > Advanced and changed the Virtual Memory to the max which is in the Gig > > > territory. I will see if this influences the need to break the export into > > > 5,000 rows. > > > > > > Phil > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > > > Behalf Of Ian Stone > > > Sent: Thursday, January 31, 2002 3:49 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: Export Algorithm > > > > > > > > > Phil > > > > > > Now you can set width to more than 256 it is possible to use select to > > > export data: > > > > > > SET VAR vht TEXT = (CHAR(9)) > > > SET EOFCHAR OFF > > > SET HEADINGS OFF > > > SET LINES 0 > > > SET WIDTH 1000 > > > SET SELMARGIN 1 > > > OUTPUT filename > > > SELECT (t1.Account_number+','+(CTXT(t2.Company_Cont_key))+.vht+ (CTXT + > > > (t3.catalognr))+.vht+'1')=1000 + > > > FROM .................... > > > OUTPUT SCREEN > > > > > > > > > At 21:36 30/01/2002 -0500, you wrote: > > > >Does anyone know what the algorithm is for Gateway Export ASCII Tab > > > >delimeted files? > > > > > > > >The reason: > > > >I have 150,000 rows of data (length) which consists of 390 character/txt. > > > >The primary key (ID) starts with 1 and is incremented by 1 for every > > > insert. > > > >So, 150,000*390 = 58.5Mb. This is what I wanted to export. > > > > > > > >When I wrote an export.rmd, I had to break the files into 5,000 > > > records/file > > > >to be able to have data in the file. > > > > > > > >What is the standard number of bytes that file will hold? Is there a > > > >standard? > > > > > > > >Phil > > > > > > > > > > > >================================================ > > > >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/ > > > > > > > > > ================================================ > > > 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/ > > > ================================================ > 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/
