> Thanks Joe, It's surprising how lonh you can look at something and not see the obvious. In this case, last% was
> way beyond the last button, but that had not bothered FB II so I didn't give it qa thought here. Dum dum! Thanks
> for the response.

Stewart

>
> From: Joe Lewis Wilkins <PepeToo@...>
> To: futurebasic@...
>
> I don't see anything in the code you've shown that would do this, but i% will
> have a value of 55 after the FOR NEXT LOOP is completed. Frankly, I've had the
> same situation and I chose to keep track of the Button that was Marked, then
> unmarking it when another one is marked.

snip

> > I am having a problem with a hidden function named  FN UnmarkBtns, which
> > I think is the root of another problem.
> > Another function draws a window with 15 buttons,  number 40 to 54 When
> > one button is clicked, the following function is called to make sure the
> > button is not marked. Here the two parameters are respectively 40 and
> > 54.
> >
> > LOCAL  FN UnmarkBtns(frst%,last%)
> >     'TRON BREAK
> >    DIM i%
> >    FOR i% = frst% TO last%
> >       BUTTON i%, _activeBtn
> >    NEXT i%
> > END FN