Export field separator question

[Nancy Palmquist]

Kenneth Brody wrote:

> John Esak wrote:
> 
>>>>Have you considered "f=253"?
>>>
>>>I wouldn't have considered that, since, clearly (:-), that means "use
>>>as the field separator (the first character of the string in) field
>>>253".
>>>
>>>:-)
>>
>>I agree with you... this is/has always been a vague inconsistency in
>>filePro.  At least, it is not intuitive since things like \r will work here
>>as well... Using just literal numbers (especially up to 3 of them) usually
>>means the contents of that field to filePro. Score 1 for you... :-)
> 
> 
> Well, if you had to put the "\n" in quotes, I might agree.  However, since
> the parameters to export flags are literal values, "f=253" doesn't refer to
> field 253 any more than "f=x" refers to field x.
> 

That makes sense but it seems vague to me that the r= and f= are so 
inconsistent with all the other assignments and will not accept 
expression logic like anything else.  I agree with John that I never 
know if I put f=10 if my field marker will be a "10" or "0a" or "^P" 
since I am not sure if it will interpret the 10 as HEX, DEC or ASC.

So this questions is an excellent one.  BTW in my book the 253 is a 
superscript 2 kind of thing, the y with two dots is 152.

-- 
Nancy Palmquist
Virtual Software Systems
PHONE: (412) 835-9417			Web site:  http://www.vss3.com