Export field separator question

[Brian K. White]

> 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.

That is why you simply should never even bother using a visual description
of a character in things like this (edi delimiter character spec), and when
the other guy is stupid enough to talk that way, don't buy into it. Somehow
you must determine an exact ascii value, or you need to know both the
character set and the nominal or descriptive name for the character.
I'm amazed how often when setting somthing like this up, that the genius at
the other end of the line is oblivious to the whole issue of character sets
and insists that if I don't know how to send him a simple u-squiggely I must
be totally incompetent to be trying to do this project. (*&^(* windows
users...

My other favorite game is having a question about line-endings, and how do
they answer? By emailing a snippet of the data of course! Just pasted right
out of who knows what screen in who knows what editor and pasted into the
body of an email. Not a zipped attachement. I scream "zipped attachement!"
how do they do it? Why, use internet explorer to ftp a .txt file from the
server to their desk, zip, attach, of course, just like you asked, you sure
are difficult but whatever if you are not smart enough to read an email I'll
accommodate... Damned "Teach yourself to be a dba in 21 hours" people really
try me. :)

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani