Checking for non-printable characters

[John Rusk]

     I'm not sure this is to the point Lindley is asking about.  Several
years ago, I ran into a situation where downloads from an IBM mainframe
sometime included non-printable characters when a certain field was blank.
I used the checksum feature of Powerhouse to identify the field and convert
it to a Powerhouse-useable blank.


----- Original Message -----
From: Lindley HILL <LHILL@doh.health.nsw.gov.au>
To: <powerh-l@lists.swau.edu>
Sent: Thursday, September 16, 1999 10:06 PM
Subject: Checking for non-printable characters


> I have the feeling this may have done the rounds a while back, but
couldn't find it.
>
> I have a request from a user to verify that all the text fields in the
system don't contain non-printable characters (i.e. other than ASCII codes
32 - 126)
>
> Is there a reasonably neat approach that can be used to check a text
field. It seems that it probably revolves around the use of the CHARACTERS
function, but I can't see how to code it efficiently.
>
> Any help would be appreciated.
>
>
> Lindley Hill
> NSW Health Dept
> Sydney, Aust
> (02) 9391 9726
>
>
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
=
> Subscribe: "subscribe powerh-l" in message body to
majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
> This list is closed, thus to post to the list, you must be a subscriber.
>

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.