RJT> You create a *.ANS file,  run ANS2MEC,  and then edit 
 RJT> the resulting *.MEC file, inserting whatever MECCA 
 RJT> codes you like.  This is the way I've done it here,  
 RJT> and I *always* end up altering the file before I even 
 RJT> start adding to it,  which is why I don't ever use 
 RJT> ANS2BBS -- you don't get to look at the intermediate 
 RJT> version of things.
While you're at it, I have a question too.  Remember I'm one of the "no files 
or ansi here" people ... only I just made an exception.  When I tried 
ans2bbs, first I got a "no such ansi character" message for one line out of a 
hundred or two.  But, worse, the resulting bbs file, when DISPLAYED by 
Oracle, was chockablock full of command codes shown as normal characters (not 
functioning).
If I go the two step route, will it fix the problem, or am I going to have to 
redo the mec files heavily before the 2nd step?  (If it's any major effort, 
this minor project goes back down the tube.)
--- Maximus 2.02
---------------