Gregg,
Look for this option QUOTELENMAX System Option, I think it should take care
of that nasty little warning.
Toby Dunn
From: Gregg Snell <***@DATASAVANTCONSULTING.COM>
Reply-To: Gregg Snell <***@DATASAVANTCONSULTING.COM>
To: SAS-***@LISTSERV.UGA.EDU
Subject: Re: WARNING: The quoted string currently being processe...
Date: Tue, 15 Feb 2005 11:15:17 -0600
MIME-Version: 1.0
Received: from malibu.cc.uga.edu ([128.192.1.103]) by mc7-f7.hotmail.com
with Microsoft SMTPSVC(6.0.3790.211); Tue, 15 Feb 2005 09:15:24 -0800
Received: from listserv.cc.uga.edu (128.192.1.75) by malibu.cc.uga.edu
(LSMTP for Windows NT v1.1b) with SMTP id <***@malibu.cc.uga.edu>;
Tue, 15 Feb 2005 12:15:23 -0500
Received: from LISTSERV.UGA.EDU by LISTSERV.UGA.EDU (LISTSERV-TCP/IP release
1.8d) with spool id 123082 for SAS-***@LISTSERV.UGA.EDU; Tue, 15 Feb
2005 12:15:23 -0500
Received: from datasavantconsulting.com
(client69-44-16-113.hardhathosting.com [69.44.16.113]) by
listserv.cc.uga.edu (8.12.11/8.12.11) with ESMTP id j1FHFMqS012039
for <SAS-***@LISTSERV.UGA.EDU>; Tue, 15 Feb 2005 12:15:23 -0500
Received: from [127.0.0.1] ([207.43.195.203]) (authenticated) by
datasavantconsulting.com (8.11.6/8.11.6) with ESMTP id j1FHFKv31109
for <SAS-***@LISTSERV.UGA.EDU>; Tue, 15 Feb 2005 11:15:21 -0600
X-Message-Info: SuyIeF3cBu+T8u5niniOCOSd0lzgxs4nQ//P6GsPjhg=
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
References: <BAY101-***@phx.gbl>
Newsgroups: bit.listserv.sas-l
Return-Path: owner-sas-***@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 15 Feb 2005 17:15:25.0058 (UTC)
FILETIME=[F024CE20:01C51381]
Toby,
But is there anyway to suppress the warning when you know you will have
strings longer than 256? This appears to be a hold-over from the old V6
days when 256 was the max character variable limit.
Thanks,
Gregg Snell
Post by toby dunnBen,
I just got done getting rid a the same message in some code I debugging
right now. You don't have to have missing quotes to get this message just
the quoted string is longer than 256 characters. Mine was coming from a
macro variable that I passed into a quoted string that in certain instances
would make the string longer than 256 so I compressed it and it worked fine
for me. In yoru case I suspect we would have to see your code to figure out
what is causeing the warning and how to fix it.
Toby Dunn
Subject: WARNING: The quoted string currently being processe...
Date: Tue, 15 Feb 2005 12:06:41 -0500
Received: from mailgw.cc.uga.edu ([128.192.1.101]) by mc7-f7.hotmail.com
with Microsoft SMTPSVC(6.0.3790.211); Tue, 15 Feb 2005 09:06:44 -0800
Received: from listserv.cc.uga.edu (128.192.1.75) by mailgw.cc.uga.edu
Tue, 15 Feb 2005 12:06:41 -0500
Received: from LISTSERV.UGA.EDU by LISTSERV.UGA.EDU (LISTSERV-TCP/IP release
2005 12:06:41 -0500
Received: from malibu.cc.uga.edu (malibu.cc.uga.edu [128.192.1.103]) by
listserv.cc.uga.edu (8.12.11/8.12.11) with ESMTP id j1FH6fgI009830
Received: from listserv.cc.uga.edu (128.192.1.75) by malibu.cc.uga.edu
(LSMTP for Windows NT v1.1b) with SMTP id
X-Message-Info: SuyIeF3cBu+/d2BQecV9WAlqNA56+1qh3VrBZlTDvok=
Newsgroups: bit.listserv.sas-l
X-OriginalArrivalTime: 15 Feb 2005 17:06:45.0332 (UTC)
FILETIME=[BA5CE940:01C51380]
Dear SAS-L
I have a long datastep that is throwing this warning on execution. It
contain some largeish SQL statements - 10 lines or so - embedded in
multiple call executes fired according to if-thens in the datastep. All in
all I get...
WARNING: The quoted string currently being processed has become more than
262 characters long. You may have unbalanced quotation marks.
...4 times on execution of the macro that contains the datastep. There
aren't any unbalanced quotation marks and the message is an annoyance. I
know its bad practise to let these messages go so was wondering if there
are any tips for resolving the situation? The datastep is 163 lines
including about ten blank lines.
Any comments much appreciated,
Ben.