RE: string editing suggestions

First, TESTN does not always perform as you expect.  Some characters, "H" or
"I" comes to mind, are interpreted as numeric by TESTN.  In fact, if you
MOVE these characters into a numeric field, the numeric field will contain a
valid numeric value.

As for the third, I don't have anything that will do that, but I would have
two arrays, one a single character array with 23 occurrences and a numeric
array with 23 occurrences.

I would use the %SUBST operation code to sequentially extract the characters
from the field.  With each character, I would determine if the character
already exists in the array.  If not, I would add the character to the array
and initialize the corresponding numeric array occurrence to 1.  If it does
exist, I would add one to the numeric array occurrence and compare the new
value to X.  If greater, end the loop and return an error.  If not, then
keep going.

Hope that helps.

Donald R. Fisher, III
Project Manager
The Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@roomstoreeast.com

<clip>
1) numeric only... easy enough with TESTN OP Code
<clip>
3) testing for non-repetitive characters (i.e. maximum of x number of
the same digits keyed...not necessarily consecutive) AND, x is based on
HOW MANY characters were keyed within the 23 character string.
<clip>