Date: Thu, 14 Aug 2008 10:26:06 -0400
Reply-To: Arthur Tabachneck <art297@NETSCAPE.NET>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Arthur Tabachneck <art297@NETSCAPE.NET>
Subject: Re: Dirty Data CSV
Curtis,
Are there any useful guidlines? For example, is the first field always
numeric, is there a minimal length to "good" records that is always
greater than the length up to the extra CRLF, or anything else that might
be useful as a pattern?
Providing a couple of sample lines would definitely help.
Art
------
On Thu, 14 Aug 2008 09:13:23 -0500, Smith, Curtis, Mr, DCAA
<Curtis.Smith@DCAA.MIL> wrote:
>I'm sure glad you guys are here.
>
>I've got a CSV file downloaded from a COGNOS data warehouse.
Occasionally, there is a record split over two rows. I will find a CRLF in
the midst of a quoted text field. SAS is treating this as two rows, rather
than ignoring the CRLF. I'm using the MISSOVER and DSD options in the
INFILE statement. The hard solution is to use a text editor, manually scan
the file for the wayward CRLFs, and delete them. I'm hoping someone has a
SAS code solution.
>
>Thanks.
>
>
>
>*-----------------------------------------*
>| Curtis A. Smith |
>| Supervisory Auditor |
>| Defense Contract Audit Agency |
>| Boeing-Huntington Beach Resident Office |
>| 5301 Bolsa Avenue M/C H014-A405 |
>| Huntington Beach, CA 92647-2099 |
>| Voice: 714-372-2601 |
>| FAX: 714-896-6915 |
>| E-Mail: curtis.smith@dcaa.mil |
>*-----------------------------------------*
>IMPORTANT: This e-mail, including all attachments, constitute Federal
Government records and property that is intended only for the use of the
individual or entity to which it is addressed. It also may contain
information that is privileged, confidential, or otherwise protected from
disclosure under applicable law. If the reader of this e-mail transmission
is not the intended recipient or the employee or agent responsible for
delivering the transmission to the intended recipient, you are hereby
notified that any dissemination, distribution, copying or use of this e-
mail or its contents is strictly prohibited. If you have received this e-
mail in error, please notify the sender by responding to the e-mail and
then delete the e-mail immediately.
|