> >ascii_string should contain chr(0)+chr(1)+...+chr(255), ebcd_string > >should contain corresponding characters in EBCDIC, or vice versa. > > Thanks for that Dragan, > We thought it would be something like what you have written above, > but we had not purchesed a communication product yet and as such, we would > prefer to purchase something that would do most of the job from the start > and not require us to code around problems that another products features > will already take care of. Well, this is quick_and_dirty, and I had an impression you needed it solved yesterday. Having a regular solution is much better, because it will handle numeric formats conversion etc; my approach goes just byte-for-byte, and probably would require some additional processing for numerics (numbers like 00043250{ do seem familiar, eh?).