QUOTELENMAX System Option

--------------------------------------------------------------------------------

Specifies that SAS write to the SAS log a warning about the maximum length for strings in quotation marks Syntax Description

QUOTELENMAX specifies that SAS write to the SAS log a warning for the maximum length for strings in quotation marks to the SAS log

NOQUOTELENMAX specifies that SAS does not write a warning for the maximum length for strings in quotation marks to the SAS log

--------------------------------------------------------------------------------

Details

If a string in quotation marks is too long, SAS writes the following warning to the SAS log:

WARNING 32-169: The quoted string currently being processed has become more than 262 characters long. You may have unbalanced quotation marks.

On 10/31/06, Howard Schreier <hs AT dc-sug DOT org> <nospam@howles.com> wrote: > On Tue, 31 Oct 2006 13:40:58 -0500, Arthur Tabachneck <art297@NETSCAPE.NET> > wrote: > > >Irin, > > > >I agree with Michael, but also think that 'database' should > >read 'datafile' and that you may end up having to also declare the > >desired 'table'. > > I usually agree with Mike too, but not this time. PROC IMPORT has all those > "data source statements" which look like options because they have equal > signs. So the semicolon belongs there. It's really atypical SAS syntax. > DATABASE= is one of the data source statements for MS Access. > > I notice that the log states that the output *was* created. Irin did not > confirm this or indicate whether the output was as expected. > > Anyway, it makes me think that the open quote may actually be somewhere > later in the code. > > > > >Further, if SAS can't handle that long of a string, you could shorten it > >using short DOS names. For example: > > > >datafile="p:\HHH\DDDDDD~1\AAAA\MMMMMM~1\Survey 8\KKKKKK~1\ > >2006\Input\Satisfaction.mdb"; > > > >HTH > >Art > >------------ > >On Tue, 31 Oct 2006 10:08:48 -0800, Irin later <irinfigvam@YAHOO.COM> > >wrote: > > > >>Michael, > >> When I took it out my program generate an error message: > >> > >> WARNING 1-322: Assuming the symbol DATATABLE was misspelled as database. > >> > >> Irin > >> > >> > >>Michael Raithel <michaelraithel@westat.com> wrote: > >> Irin, > >> > >>You have an errent semicolon: "dbms=access;". That is probably messing > >>up your PROC IMPORT statement. Check it out! > >> > >>Take Care! > >> > >>----MMMMIIIIKKKKEEEE > >>(aka Michael A. Raithel) > >> > >> > >>> -----Original Message----- > >>> From: owner-sas-l@listserv.uga.edu > >>> [mailto:owner-sas-l@listserv.uga.edu] On Behalf Of Irin later > >>> Sent: Tuesday, October 31, 2006 9:47 AM > >>> To: SAS-L@LISTSERV.UGA.EDU > >>> Subject: The quoted string > >>> > >>> > >>> Hi, > >>> This is a piece of code: > >>> > >>> proc import table='hfbc65Int' > >>> 6 out=hfbc65Intout > >>> 7 dbms=access; > >>> 8 > >>> database='p:\HHH\DDDDDDDDDDDDDDDDD\AAAA\MMMMMMMMMMMMMMMMMMMMMM > >>> MM \Survey > >>> 8 ! KKKKKKKKKKKKKKKKK Qqqqqqqqqq\2006\Input\Satisfaction.mdb'; > >>> 9 userid='***'; > >>> 10 password=' '; > >>> 11 workgpdb='***'; > >>> 12 run; > >>> > >>> > >>> After running my code above, I got the following Warning in my Log: > >>> > >>> > >>> WARNING 32-169: The quoted string currently being processed > >>> has become more than 262 characters > >>> long. You may have unbalanced quotation marks. > >>> NOTE: WORK.HFBC65INTOUT was successfully created. > >>> NOTE: PROCEDURE IMPORT used: > >>> real time 1.29 seconds > >>> cpu time 0.10 seconds > >>> > >>> Considering that I need a full path....How can I modify the > >>> code in order to eliminate this Warning message in the log? > >>> Thank you in advance, > >>> > >>> Irin > >>> > >>> > >>> > >>> --------------------------------- > >>> Want to start your own business? Learn how on Yahoo! Small Business. > >>> > >> > >> > >> > >>--------------------------------- > >>Everyone is raving about the all-new Yahoo! Mail. >