Brian, thanks for the suggestions.  I'll try them.   Meanwhile, it  
might be worthwhile to edit the 'Keyword support' part of the FBtoC  
help file so that it doesn't indicate that the SCROLL BUTTON command  
is fully supported.
>
> Attaching a scroll button to an FB Edit field using FB's Scroll  
> Button statement doesn't work in FBtoC. There was a discussion on  
> the list about this topic back in March when Walter was trying the  
> same thing. We recommended HITextViews then and it is still a good  
> idea. I don't know when/if this will be resolved. Don't hold your  
> breath.
>
> My suggestion is to look at the FBtoC example mentioned in the  
> earlier email. Not only does it move you to a scrolling text view  
> that works, but it also uses a more modern way to use external  
> resources ( like text or whatever ).
A couple of simpleminded questions:
1.  If I go this route (as seems likely), I'll have roughly 80 text  
files (.rtf format) that are used in various aspects of my program's  
Help windows.  Is there some way to access them from a folder within  
the overall project folder?  I couldn't get this to work with simple  
experimentation.


2.  Given that I'll need to call one of those 80 or so text files at a  
time into the help window, in the code in the 'scrolling text view'  
examples (I'm using 10.3), is there a way to pass different text file  
names, i.e.:

helpfilename$ = "some file name.rtf"
fn BuildUI (helpfilename$)

I tinkered a bit but couldn't get that to work either.

Thanks.

________________________________________
Mark Chappell, Professor
  Biology Department
University of California, Riverside, CA 92521, USA
      Office:  2312 Spieth, 951 827-7709 ; fax -4286
      Lab:  University Lab Building 104, 951 827-6418
      email:  chappell@...
      web:  http://biology.ucr.edu/people/faculty/Chappell.html