Thanks, I'm going with this answer. Worst case is some more reboots :)

Chris.Young@... wrote:
> 
> Looked at page 254 of the handbook, which says:
> 
> CALL SELITEXT(dItmH&, dItem%, startSel%, endSel%)
> 
> This is just plain wrong...the dItmH& should actually be dPtr&. I think
> it is because GETITEXT and SETITEXT immediately preceed SELITEXT, and
> those two traps do require the itemHandle rather than the dialog
> pointer. IM is correct.